Results 1 to 2 of 2

Thread: "Script not responding" on destroy

  1. #1

    Question "Script not responding" on destroy


    I have a TabPanel and some of the (Sub)Panels are very complex (>500 Elements (Panels, Grids, Fields, etc)). When I now close (destroy) the SubPanel my Browser (Firefox, IE) tell me on slower machines that the "Script is not responding" and I can choose to stop the script or to continue it.

    Can someone tell me how to avoid this message. Is there a way to destroy a bigger form in chunks with a timeout of some milliseconds or something else?

    I'm using ExtJS 3.0.0.

    Thanks and best regards...

  2. #2
    Sencha User's Avatar
    Join Date
    Mar 2007
    DC Area =)


    Ext JS 3.0.0 had some serious speed issues. What I would suggest is trying to figure out a way to optimize what you're doing. >500 components on screen seems like a lot and you might be doing some unnecessary things.

    If you don't want to go through your code and search for ways to clean things up, you could manage the destruction yourself. There are 'before' (beforeclose, beforedestroy) events that you can hook into and destroy the child items yourself. Just be aware that setTimeOut will "fork off" an asynchronous JavaScript execution stack causing timing issues.

Similar Threads

  1. Removing large component causes "stop running this script" error
    By jweber in forum Ext 2.x: Help & Discussion
    Replies: 18
    Last Post: 3 Feb 2010, 2:22 AM
  2. Replies: 3
    Last Post: 28 Oct 2009, 6:38 AM
  3. "Stop running this script" error when rendering combos
    By nanich in forum Ext 2.x: Help & Discussion
    Replies: 19
    Last Post: 12 Aug 2009, 11:40 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts