Rob Cottingham

Meeting your social media humor needs since 1963

Search:

12 May 2006

Firefox timeout tip: goodbye, unresponsive script

Bookmark and Share
Category: How to...; Technology

I love Firefox, the open-source web browser with a zillion and one little extensions and options. But there are maddening little quirks – like the way it turns uploading a largish file into an ordeal.

It’s something to do with the way Firefox handles scripts: impatiently. If something hasn’t happened for the last five seconds, Firefox alerts you with an “Unresponsive script” error, and asks you if you want to continue. Five seconds later, another dialog box. And another. And another, until the upload finally completes.

It turns out you don’t have to live with the heartbreak of Firefox’s short attention span. Instead, you can give it a quick dose of digital Ritalin with this handy, easy tip (from Lifehacker, by way of the Computer Vet blog):

  1. Type about:config in Firefox’s address bar.
  2. Filter down to the value for dom.max_script_run_time.
  3. Change the value to something higher than the default (which is 5.) I set mine to 20.

You do the filtering in step 2 by typing “dom.m” in the “Filter” bar that appears at the top of the page. Then double-click on the number that appears in the “Value” column. A dialog box pops up, where you enter your new numerical value; I used 100.

By the way, the dom.max_script_run_time value is the number of seconds Firefox should wait before asking “Are we there yet?” Bear in mind that you probably won’t be able to use Firefox at all while a script is running, so ask yourself how long you want to potentially be shut out of your browser.

If you want, you can set the value to 0, which Firefox takes to mean “Shut up and run the damn thing” – great if you don’t want to be interrupted, but maybe not so great if you run into some buggy Javascript.


  • http://www.darrenbarefoot.com Darren

    God bless you, good sir.

  • http://www.robcottingham.ca/roblog Rob

    I see I’m not the only one. :)

    It’s amazing just how long I can live with a bug, thinking “Well, that’s just the way it is,” before I finally break down and try to do something about it.

    And more often than not, it turns out there’s a solution within easy reach.

    So far, though, the problem I’m having with WordPress and TinyMCE’s substituting line breaks for paragraph breaks remains unresolved…

  • http://www.matteoraggi.com Matteo Raggi

    Which is the maximum number for the firefox script timeout?
    Somewhere I was reading 20, butr firefox permit me to insert biggest numbers..

  • http://velkr0.org velkr0

    thank you!! thank you!! waiting is sooo much easier than waiting and clicking continue and waiting some more… ;)

    cheers!

  • http://www.muzika.dk Sasa

    Thanks dude :)!
    http://www.muzika.dk

  • http://kb.mozillazine.org/Unresponsive_Script_Warning Steve Chapel

    There’s more information about the issue at
    http://kb.mozillazine.org/Unresponsive_Script_Warning

  • Michael Soria

    Alternately, just enter “about:config” in the FF address bar, press “Enter”, scroll down to “dom.max_script_run_time”, double-click the entry, and change its value. Then close the tab. Restart may not be necessary, but I am not sure.

  • howard

    This fix does not help. It just lets the screen sit there longer before you get the script error again. So what?

  • http://www.robcottingham.ca/ Rob

    Two possibilities jump to mind, but I hope others will weigh in:

    • You could try increasing the size of the new value, if the script or upload needs more time to execute.
    • It’s not impossible that there’s actually a malfunctioning script or a connection problem with your upload, and that Firefox is reporting a genuine error.

    Good luck!

  • Joel

    Worked for me !

  • David

    I tried setting the value to 0 and the result was that Firefox wouldn’t launch at all!!! Ended up having to restart in Safe Mode and set the value back to the default. A very frustrating exercise!

  • http://www.robcottingham.ca/ Rob

    Yikes! But nice try – that could have been a killer idea!

  • http://westendgirl.ca Ariane

    Hah, I just googled this and guess what the #1 result was! :-) Thanks for the tip, worked great!

  • http://snailware.blogspot.com app

    This tip also works well for K-Meleon browser, which runs quite well on old slow pc’s except for this annoyance.

    Following your instructions can make life livable for those with really slow machines.

    I entered “30″ for the value, for use on a 233mhz machine, and it reduced that nag to “rare”

  • Pingback: How a popular (but off-topic) blog post can boost the rest of your content | Social Signal

Watch my YouTube channel

Creative Commons License This work is licensed under a Creative Commons Licence. Please attribute to Rob Cottingham with a link to the content's original page on this web site. For more information, contact Rob at rob@robcottingham.ca.

Powered by WordPress, state-of-the-art semantic personal publishing platform

Find out about the other tools this site uses

Get Rob's latest cartoons hot off the press! (How retro is that?)

Subscribe to Noise to Signal by email, and you never need to miss another snort, guffaw, giggle or ironically-raised eyebrow.

Your email address:

Delivered by FeedBurner. Be advised, I won't sell, rent, lend or skywrite your email address. That's not how I roll.