British Inside

An Englishman living in small town America

James Shaw


  • Copyright James Shaw 2004-2007

    Creative Commons License

    View James Shaw's profile on LinkedIn

Firefox Unresponsive Script

After the first few thousand times you get this warning it starts to get old. Real Old.

I always thought it was a badly written site like OnTime or just because I can at times have 20 tabs open in FF3 testing different versions of the site all running loads of scripts and silverlight.

But today I'd had enough. I googled it, which is what I should have done a long time ago. You'll find a lot of people babbling about Firebug and other add-ins, but it's a bug in Firefox that's the issue.

Jaime explains it perfectly here.

Although Jaime is trying to explain how site developers can help, I really just want my FF3 to start behaving. The nugget is right at the bottom:

Firefox controls its time out based on the dom.max_script_run_time setting, which you can tweak via the about://config moniker; the default timeout in most recent versions is 10 seconds.

Actually, you need to type about:config into FF3 to see this config (I had no idea this existed).

I then changed both dom.max_script_run_time and the one above it (chrome something) to 60 seconds. Hopefully that will fix it once and for all. Fingers crossed.

Posted: Friday, July 11, 2008 1:12 PM by James


Dan Hounshell said:

Tips like this are the reason I love subscribing to your blog, James. Thanks.
# July 12, 2008 4:50 PM
New Comments to this post are disabled