I have a solution to this here:
http://www.picnet.com.au/blogs/Guido/post/2010/03/04/How-to-prevent-Stop-running-this-script-message-in-browsers.aspx

It basically just breaks up long/expensive tasks into manageable chunks. Works really well and stops those pesky ’stop running this script’ dialogs.

Thanks

Guido

here is the html which was causing this problem.

this html is missing before

after correcting it to below html i never got that message again.

The article says that the value defaults to 5,000,000. So I guess, you set it to less than that if you want the popups more often, or more than that if you want the popups less often.

Tim

So, I am trying to edit the HKEY_CURRENT_USER\Software\Microsoft\InternetExplorer\Styles key in the registry. What value do you use to the desired number of script statements, and how, exactly (menu items, specific key actions) do you do this.

I feel like I am left high-and-dry when Micorsoft just says “Create a new DWORD value called “MaxScriptStatements” under this key and set the value to the desired number of script statements” and does not tell you how or what the value should be!

What should the value be and how do I set it?

HELP!

I agree; running tests is perhaps the main exception.

The IE case is worst, since the dialog pops up every second. However in all cases I reckon there should be a “don’t show again” option of some kind, valid perhaps for the current session only. That would give the user an easy solution for those cases where she does want the operation to complete.

Incidentally I didn’t see this on Flash 9 because my test completed in less than 20 seconds

Tim

It is not practical to set the values on users machines, so you have to find ways around it. One way is to break it up using setInterval() to avoid having one long loop, so that it calls the same function but gives it a different block of data to work on. Usually, if you have some script which is taking that long to execute, there is probably an issue with how you are doing things. For instance, one common error is to add rows to a grid one at a time, which results in one complete grid redraw for each row. Much more efficient is to add rows to an array first, then assign the entire array to your grid component.

You can do code profiling with Firefox if you install the debugger extension (FireBug does this as well I believe). The profiler will tell you exactly how long each function is taking to run.

That article didn’t turn up when I Googled for some reason.

Tim