Dom.max script run time
Possible values and their effects
The value is a positive integer, determining the number of seconds of execution before warning. 0 and negative values are considered "forever." (Default value is 10; 5 in versions prior to nightly builds dated 2006-07-27) (bug 335058)
In builds prior to 2005-10-11, values less than 0 were assumed to be the default (then, 5). In builds prior to 2006-07-27 (e.g., Firefox 1.5), this preference affected scripts running in content and chrome; the limit on scripts running in chrome is now determined by dom.max_chrome_script_run_time.
- This preference was not dynamic (i.e., only read at startup) until 2005-10-11. The new dynamic behavior is available in Firefox and Thunderbird versions 1.5 and later, and in all versions of SeaMonkey.
- This preference was subject to some bugs (see below) that made the true time limit somewhat unpredictable for certain scripts.
If you’re encountering the “A script on this page is causing Mozilla to run slowly” dialog often and you’d like to disable it, setting this preference to 0 will allow the script to run for as long as it needs. A large number may be more appropriate, though, to avoid locking the entire UI forever as the script executes.
First checked in
Has an effect in
- Mozilla Suite (all versions since 1.7a)
- Mozilla Thunderbird (all versions since 0.6)
- Camino (all versions since 0.8b)
- Mozilla Firefox (all versions since 0.9)
- SeaMonkey (all versions)
- Bug 13350 - DOM needs to police JS infinite loops, schedule garbage collection
- Bug 230909 - ability to disable "this script is running slowly" dialog
- Bug 247225 - dom.max_script_run_time parameter doesn't work as expected
- Bug 302333 - Inappropriate 'Unresponsive Script' warning
- Bug 335058 - script timeout too small in firefox