Confirmed users
1,982
edits
Electrolysis/plugins: Difference between revisions
→Preferences related to plugins and process timeouts
| (24 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Plugins and e10s | = Plugins and e10s = | ||
== Preferences related to plugins and process timeouts == | |||
=== Platform Prefs === | |||
{ | {| 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. | |||
|} | |||
== | === Windows specific === | ||
{ | {| class="wikitable" | ||
|- | |||
! Preference !! Default !! Description | |||
|- | |||
| dom.ipc.plugins.hangUITimeoutSecs || 11 || How long a chrome to plugin synchronous IPC message is allowed to process before we display the plugin hang dialog. | |||
|- | |||
| dom.ipc.plugins.hangUIMinDisplaySecs || 10 || Minimum time that the plugin hang UI will be displayed. | |||
|- | |||
| dom.ipc.plugins.flash.disable-protected-mode || false || We set this if we detect multiple chrome hangs during a session. We do not set it back. Active in both non-e10s and e10s. | |||
|} | |||
=== Firefox Specific === | |||
{| class="wikitable" | |||
|- | |||
! Preference !! Default !! Description | |||
|- | |||
| dom.ipc.reportProcessHangs || false in debug builds, true otherwise || Enable or disable the ipc ProcessHangMonitor. | |||
|} | |||
No timeouts are set for DEBUG builds, see all.js and firefox.js. | |||
== typical messaging deadlocks == | == typical messaging deadlocks == | ||
| Line 46: | Line 79: | ||
<pre> | <pre> | ||
chrome | chrome | sync ipc -> plugin | ||
chrome -> sync ipc -> content -> sync ipc -> plugin | sync ipc -> chrome | |||
chrome -> sync | |||
</pre> | </pre> | ||
* | * {{bug|1093693}} | ||
<pre> | <pre> | ||
chrome -> sync | chrome -> sync sendmessage -> plugin -> sync ipc -> content -> sync ipc -> chrome | ||
</pre> | </pre> | ||
* | * happens while chrome is dispatching messages, or in a sync/rpc ipc call. | ||
* we have assertion mechanisms to warn about this in non-e10s. | |||
* {{bug|1098057}} | |||
<pre> | <pre> | ||
chrome -> sync ipc -> content | chrome -> sync ipc -> content -> sync ipc -> plugin -> sync sendmessage -> chrome | ||
</pre> | </pre> | ||
* | * {{bug|1098055}} | ||
<pre> | <pre> | ||
| Line 76: | Line 104: | ||
** there's no hang dialog | ** there's no hang dialog | ||
** we have bugs on dealing with content hangs which overlap this | ** we have bugs on dealing with content hangs which overlap this | ||
** | ** {{bug|1096664}} | ||
== plugin deadlock == | == plugin deadlock == | ||
| Line 115: | Line 143: | ||
Follow up: | Follow up: | ||
* {{bug|1095754}}: Sync remote plugin widget clipping, bounds, and visibility with the render frame | * {{bug|1095754}}: Sync remote plugin widget clipping, bounds, and visibility with the render frame | ||
* file a support request fishing for help? | |||
== follow up bugs == | == follow up bugs == | ||
| Line 123: | Line 152: | ||
* {{bug|1095761}}: Fixup Windows focus routing in the PluginInstances for e10s | * {{bug|1095761}}: Fixup Windows focus routing in the PluginInstances for e10s | ||
* {{bug|1095776}}: Deal with spurious WM_PAINT messages on plugin parent windows | * {{bug|1095776}}: Deal with spurious WM_PAINT messages on plugin parent windows | ||
* {{bug|1098055}}: Sync SendMessage calls from plugin may deadlock in the new plugin model | |||
* {{bug|1098057}}: Sync SendMessage calls from chrome may deadlock in the new plugin model | |||
* {{bug|1096664}}: Plugin hang detector is currently disabled with e10s | |||
* {{bug|1096080}}: ProcessFirstMinidump processing appears broken | |||