No issue - Tighten default script time-outs and expose stop_slow_scripts

The timings here are still slightly more lenient than the hard-coded
fallback timings in code (10/20 for content/chrome respectively) but
we definitely should not need very long time-outs by default on Chrome
scripts anymore.

Also exposes dom.always_stop_slow_scripts to about:config since we're
making it also UI-configurable in Pale Moon and it just makes sense not
to hide this option.
This commit is contained in:
Moonchild 2023-12-29 22:56:38 +01:00 committed by roytam1
commit 0bcbbafa73

View file

@ -2752,8 +2752,11 @@ pref("editor.resizing.preserve_ratio", true);
pref("editor.positioning.offset", 0);
pref("dom.use_watchdog", true);
pref("dom.max_chrome_script_run_time", 90);
pref("dom.max_script_run_time", 20);
pref("dom.max_chrome_script_run_time", 30);
pref("dom.max_script_run_time", 15);
// Automatically terminate non-responsive scripts if script_run_time expires.
pref("dom.always_stop_slow_scripts", false);
// Stop all scripts in a compartment when the "stop script" dialog is used.
pref("dom.global_stop_script", true);