Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

  1. #1
    Sencha User
    Join Date
    Aug 2012
    Location
    Hyderbad
    Posts
    3
    Vote Rating
    0
    MadhusudhanT is on a distinguished road

      0  

    Default Unanswered: Script busy error message

    Unanswered: Script busy error message


    Hi All,
    In our application, we are using GWT 2.2.0 and GXT 2.2.3. In this, we have most of the functionality depending on the grid operations like hiding/deleting the rows, calculating the cell values of the row & adding the same to another grid, applying colors to the cell values based on some conditions. Some windows have more than 2 grids.



    Here, my problem is : If we get more than 100 records from the DataBase , we are getting an alert box “Warning:Unresponsive script” stating “A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete” in all browsers.

    We are also getting the same warning message in IE7 browser even though the no.of records are less than 100.



    Can anyone help me to resolve this issue.

    Thanks in advance,
    Madhusudhan T.

  2. #2
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,716
    Answers
    109
    Vote Rating
    87
    Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light

      0  

    Default


    Are you loading both grids at the same time? Are these grids very large (many columns)? Are you testing in Web Mode? Dev Mode is expected to take longer, and may produce more of these warnings, but does not mean that web mode will as well.

    You say you are seeing this in IE7 - The script error warnings in IE arrive not because of the amount of time the code has been running, but because of the number of JavaScript operations. After some limit is reached, IE pauses running JavaScript and asks the user if they want to keep going. This means that writing 'less expensive' that still take the same number of instructions will not fix this kind of problem - nor will using a faster computer.

    Instead, you usually need to break the problem into smaller pieced. If both grids are being filled at once, consider breaking that into two deferred commands (using the GWT Scheduler class). If these are very wide grids, you might possibly need to load each one in batches.

    More details about your problem or specific code samples will make it easier to provide a solution. You may find it helpful to start with an example at http://sencha.com/examples-2/ and make it more complex until it hits this same issue, then share that so there is a complete example we can run.

Thread Participants: 1