Dom.max chrome script run time: Difference between revisions
From MozillaZine Knowledge Base
Jump to navigationJump to search
| Line 20: | Line 20: | ||
==Related bugs== | ==Related bugs== | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=335058 Bug 335058 - script timeout too small in firefox] | * [https://bugzilla.mozilla.org/show_bug.cgi?id=335058 Bug 335058 - script timeout too small in firefox] | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=482811 Bug 482811 - Unresponsive script timeout can cause hang if file dialog open (attachment, save file etc)] | |||
==Related preferences== | ==Related preferences== | ||
Revision as of 23:41, 26 August 2012
Background
JavaScript that takes a long time to run can make the browser unresponsive. As such, a check is built in to allow long-running scripts to be aborted. That check is now able to differentiate between scripts running in web pages (content) and scripts running in the application’s chrome. This preference determines how long scripts running from chrome are allowed to run before the user can choose to abort the script.
Possible values and their effects
The value is a positive integer, determining the number of seconds of execution (wall time). 0 and negative values are considered “forever.” Default value is 20.
Since 2012-08-21 trunk builds, new default on Windows and Mac is 0 (bug 482811).
Caveats
- This preference only controls scripts running with chrome privileges. For scripts with content privileges, see dom.max_script_run_time.
First checked in
Has an effect in
- Mozilla Firefox (nightly builds after 2006-07-27; 2.0)
Related bugs
- Bug 335058 - script timeout too small in firefox
- Bug 482811 - Unresponsive script timeout can cause hang if file dialog open (attachment, save file etc)
