Bug 1123956 - [e10s] Tweak timeout values for slow script UI (r=mrbkap)

This commit is contained in:
Bill McCloskey 2015-01-20 15:42:05 -08:00
parent 1f72ae7acc
commit d4251df9d3
2 changed files with 4 additions and 4 deletions

View File

@ -20,10 +20,10 @@ Cu.import("resource://gre/modules/Services.jsm");
*/
/**
* If a hang hasn't been reported for more than 5 seconds, assume the
* If a hang hasn't been reported for more than 10 seconds, assume the
* content process has gotten unstuck (and hide the hang notification).
*/
const HANG_EXPIRATION_TIME = 5000;
const HANG_EXPIRATION_TIME = 10000;
let ProcessHangMonitor = {
/**

View File

@ -2278,7 +2278,7 @@ pref("editor.positioning.offset", 0);
pref("dom.use_watchdog", true);
pref("dom.max_chrome_script_run_time", 20);
pref("dom.max_child_script_run_time", 2);
pref("dom.max_child_script_run_time", 10);
pref("dom.max_script_run_time", 10);
// If true, ArchiveReader will be enabled
@ -2327,7 +2327,7 @@ pref("dom.ipc.plugins.timeoutSecs", 45);
pref("dom.ipc.plugins.parentTimeoutSecs", 0);
// How long a plugin in e10s is allowed to process a synchronous IPC
// message before we notify the chrome process of a hang.
pref("dom.ipc.plugins.contentTimeoutSecs", 2);
pref("dom.ipc.plugins.contentTimeoutSecs", 45);
// How long a plugin launch is allowed to take before
// we consider it failed.
pref("dom.ipc.plugins.processLaunchTimeoutSecs", 45);