Electrolysis/plugins: Difference between revisions

Electrolysis/plugins (view source)

Revision as of 12:56, 6 May 2015

260 bytes added , 6 May 2015

→‎prefs system for timeouts

Jmathies

Confirmed users

1,982

edits

@@ Line 1: / Line 1: @@
 = Plugins and e10s =
-== prefs system for timeouts ==
+== Preferences related to plugins and process timeouts ==
+{| class="wikitable"
+|-
+! Preference !! Default !! Description
+|-
+| dom.ipc.plugins.timeoutSecs || 45 || How long a chrome to plugin synchronous IPC message is allowed to process before we consider it "hung".
+|-
+| dom.ipc.plugins.contentTimeoutSecs || 10 || How long a content to plugin synchronous IPC message is allowed to process before we notify the chrome process of a plugin hang.
+|-
+| dom.ipc.plugins.processLaunchTimeoutSecs || 45 || How long a plugin launch is allowed to take before we consider it failed.
+|-
+| dom.ipc.plugins.parentTimeoutSecs || -1 || How long a plugin process will wait for a response from the parent to a synchronous request before terminating itself. After this point the child assumes the parent is hung. Currently disabled.
+|-
+| dom.ipc.reportProcessHangs || true || Enable the e10s plugin hang monitor.
+|}
-'''dom.ipc.plugins.timeoutSecs (45)''' How long a chrome to plugin synchronous IPC message is allowed to process before we consider it "hung".
+=== Windows specific ===
-'''dom.ipc.plugins.contentTimeoutSecs (10)''' How long a content to plugin synchronous IPC message is allowed to process before we notify the chrome process of a plugin hang.
+{| class="wikitable"
+|-
-'''dom.ipc.plugins.processLaunchTimeoutSecs (45)''' How long a plugin launch is allowed to take before we consider it failed.
+! Preference !! Default !! Description
+|-
-'''dom.ipc.plugins.parentTimeoutSecs (0)''' How long a plugin process will wait for a response from the parent to a synchronous request before terminating itself. After this point the child assumes the parent is hung. Currently disabled.
+| dom.ipc.plugins.hangUITimeoutSecs || 11 || How long a chrome to plugin synchronous IPC message is allowed to process before we display the plugin hang UI.
+|-
-Windows specific
+| dom.ipc.plugins.hangUIMinDisplaySecs || 10 || Minimum time that the plugin hang UI will be displayed.
+|}
-'''dom.ipc.plugins.hangUITimeoutSecs (11)''' How long a chrome to plugin synchronous IPC message is allowed to process before we display the plugin hang UI.
-'''dom.ipc.plugins.hangUIMinDisplaySecs (10)''' Minimum time that the plugin hang UI will be displayed.
 No timeouts are set for DEBUG builds, see all.js