This thread was archived. Please ask a new question if you need help.
If my max_script_run_time setting is 10, why does it often take Firefox a minute or longer to prompt me to stop an unresponsive script?
My browser frequently crashes due to unresponsive scripts, often when I have Google tabs open (google docs, gmail, etc). This wouldn't be such a big problem if Firefox didn't wait so long to give up on these scripts. Firefox sometimes waits a minute or longer, it seems. Sometimes a few minutes. My max_script_run_time setting is 10, so shouldn't FF prompt to stop an unresponsive script after 10 seconds?
All Replies (3)
Just to be complete.
There are two prefs to control that maximum, one for website code and another for chrome (extension) code.
@cor-el, would the chrome extension setting affect Firefox?
@ideato, the only enabled extension is firebug.
I don't think my problems are due to extensions in this case. I think my problems are mainly due to various google services (gmail, docs) bugging out. What I'd love is to turn on some setting in Firefox that will give me the ability to abort a page if gets stuck for 20 seconds. I don't know specifically what I mean by "get stuck" in this case. Since some of these web pages never really stop running scripts, or continue running them periodically, it might be hard to define what is the end of a page load and when a page has finished rendering successfully. I just find that at least a couple times a day, FF freezes up, and it's almost always when I have tabs open for one or more google websites. There is often no way un-freeze things. The scripts will continue running for several minutes and FF never presents me with any opportunity to abort. I'm running Ubuntu, so there is no CTRL+ALT+Delete option, and in some cases I have to unplug the computer and pull the battery out because FF becomes completely unresponsive and causes the computer to freeze up. In short, I wish FF knew when and how to give up on a web page.