[CLOSED] Stop running this script?

  1. #1

    [CLOSED] Stop running this script?

    My main application page works beautifully under Firefox, Chrome, and IE 10. Unfortunately, under IE 8 - which unfortunately is the most common browser for my audience - I'm getting the dreaded "Stop running this script?" error. The application page in question is pretty complex, and I am running it in profiler to try to figure out where all the calls are, but it's slow going. I was wondering if you have any general suggestions for things to look for in my code (for instance, could it be that my grid has too many columns and too many filters, or that I am hiding too many columns?).

    Thanks!

    PTR
    Last edited by Baidaly; Nov 05, 2013 at 9:06 PM. Reason: [CLOSED]
  2. #2
    Hello!

    It's really difficult to say something without any details. It depends on what components you use and what they do. Different components causes different problems. But always it's better to render components only when they are required.

    Is it possible to provide at least one page that causes problems?
  3. #3
    Hi,

    Quote Originally Posted by ptrourke View Post
    for instance, could it be that my grid has too many columns
    Yes, it could be. "rows * columns" highly affects on the performance. If something might be OK for modern browsers (like Chrome, FireFox and IE10), it might be too heavy for legacy browsers like IE8 due to its weakness.

    Here is some links with tips for optimization an application:
    http://forums.ext.net/showthread.php?15699
    http://forums.ext.net/showthread.php?13726
    http://www.sencha.com/blog/ext-js-4-1-performance/
    http://www.sencha.com/blog/optimizin...d-applications
    http://www.sencha.com/forum/showthre...Best-Practices
  4. #4
    I think I have it. Will post when I know for sure.
  5. #5
    Thank you both.

    I had already tried using a grid with fewer rows per page (15 down from 25); it did speed things up. I also eliminated an unnecessary call to getCount() and rearranged a few other things so they only fired when needed (and am loading a few tabbed grids only on the BeforeShow listener).

    It looks like what really sped things up was eliminating grid columns that would rarely be used. I was hiding them by default, and have a "show details" function on a context menu that shows the values for those columns. Eliminating 7 of my 30 columns cut the function call "count" (IE's metric) by 25% down to 3.7 M. I guess the performance of the page is dominated by this grid, and it really is O(m*n).

    Thank you for the performance recommendation links, I've read through them and learned a few things I didn't realize.

    Please close.

Similar Threads

  1. IE Error : Stop running this script?
    By pooja in forum 1.x Help
    Replies: 5
    Last Post: Nov 07, 2011, 7:22 AM
  2. [CLOSED] Tasks stop running after store.save() is called
    By peter.campbell in forum 1.x Legacy Premium Help
    Replies: 7
    Last Post: Oct 11, 2011, 9:06 AM
  3. [CLOSED] Error:Stop running this script
    By pbsoft in forum 1.x Help
    Replies: 2
    Last Post: Aug 05, 2010, 3:30 PM
  4. Replies: 2
    Last Post: Jul 29, 2009, 1:57 PM
  5. Problem when running on IE7 XP
    By paapee in forum 1.x Help
    Replies: 0
    Last Post: May 21, 2009, 1:30 AM

Posting Permissions