Results 1 to 4 of 4
  1. #1
    Member
    Join Date
    Jun 2011
    Location
    ldn
    Posts
    5

    IE script warning

    Hi, we've been having significant trouble on our lightstreamer based web app with the IE script warning appearing from time to time in ie8. We haven't ruled out the possibility of our app's code causing this, but I wondered if there was any history of problems with this warning and use of lightstreamer? For instance, any usage patterns to avoid, specific to lightstreamer. Does each update consumed by lightstreamer run in a seperate JS-worker? I may try introducing worker queue-timeout style processing at various points to see if it has an impact.

    We're using several non visual tables subscribed to around 10-30 items each, pushing that data into ExtJS grids. There's no general problem with speed of the browser or CPU usage. The visual symptom is that after anything between 10 minutes and several hours of use, one of the tables stops rendering any updates for a few seconds (though the stream of updates should be constant), and then seems to consume a lot of updates (on the order of tens), triggering the slow script warning. This can happen just as frequently while using other functions on the site as when leaving the browser idle. Thanks for any light you can shed on this issue.

  2. #2
    Power Member
    Join Date
    Jul 2006
    Location
    Cesano Maderno, Italy
    Posts
    784
    Does each update consumed by lightstreamer run in a seperate JS-worker?
    no it doesn't.

    I haven't heard of anything similar to your issue before so that I haven't specific suggestions for you. Usually the heavy part is the DOM manipulation; try to remove any update on the screen to see if the browser still have the issue.

    If the issue is still there you may use IE8's developer tools profiler and try to understand where time is spent.

    Also note that the client will switch to a polling session if the slowing-algorithm is enabled and the client is slow handling the updates; see http://www.lightstreamer.com/docs/cl...SlowingEnabled. Is the algorithm enabled on your application? Do you notice the client switching to polling in your onStatusChange callback?

    HTH.

  3. #3
    Member
    Join Date
    Jun 2011
    Location
    ldn
    Posts
    5

    Post

    Quote Originally Posted by Mone
    no it doesn't.

    I haven't heard of anything similar to your issue before so that I haven't specific suggestions for you. Usually the heavy part is the DOM manipulation; try to remove any update on the screen to see if the browser still have the issue.

    If the issue is still there you may use IE8's developer tools profiler and try to understand where time is spent.

    Also note that the client will switch to a polling session if the slowing-algorithm is enabled and the client is slow handling the updates; see http://www.lightstreamer.com/docs/cl...SlowingEnabled. Is the algorithm enabled on your application? Do you notice the client switching to polling in your onStatusChange callback?

    HTH.
    Thanks for the reply. We've just implemented this kind of pattern for itemUpdate
    Code:
    table.onItemUpdate = function (item, itemUpdate, itemName) {
    	...
    	setTimeout(function () {
    		handleItemUpdate(...)
    	}, 0);
    	...
    };
    And it appears to have made a difference - IE can now run for a much longer time, so far no script warnings - without any noticeable performance hit. There is a huge hit to performance in FF so we're only doing this in IE.

    You're of course correct about the DOM manipulation; it probably is the source of these problems. I forced polling and streaming separately, and saw the same behaviour in each test. The app wasn't switching to polling automatically, and it is allowed to by default.

  4. #4
    Power Member
    Join Date
    Jul 2006
    Location
    Cesano Maderno, Italy
    Posts
    784
    glad you solved.

    anyway please note that UpdateItemInfo instances are reused by the library so do not use them in your setTimeout closure, save the needed values and use that instead.

    Good:


    Bad:


    HTH

 

 

Similar Threads

  1. Replies: 5
    Last Post: December 23rd, 2010, 08:34 AM
  2. Unresponsive Script
    By vaduganathan in forum Client APIs
    Replies: 1
    Last Post: March 23rd, 2010, 02:38 PM
  3. Action script
    By Cyro in forum Client APIs
    Replies: 30
    Last Post: July 24th, 2009, 01:50 PM
  4. Multiple connection warning alerts from Firefox
    By Waddy in forum Client APIs
    Replies: 4
    Last Post: May 14th, 2007, 02:38 PM
  5. Deprecation warning in the LiteralBasedProvider
    By jsharpe in forum Client APIs
    Replies: 1
    Last Post: April 19th, 2007, 09:24 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 04:54 PM.