This bug was filed from the Socorro interface and is report bp-ccc41702-dea7-4db7-8685-3a3462160311. ============================================================= Looking at this report we're the website is doing a sync XHR from the unload event on shutdown. Hitting the network can take an arbitrary amount of time. This causes us to hit the shutdownhang code before the user has a tab that force an XHR request on shutdown. We should consider giving website a budget for how much time they can spend in their unload before we move on. Ideally this would be a subset of the shutdownhang trigger time so that we can survive having at least a few bad apples before we take down the browser.
khuey mentions that: 1) Web workers have some kind script timeout on shutdown. 2) We could abort network loads on shutdown.
Here's the relevant Web worker code: http://mxr.mozilla.org/mozilla-central/source/dom/workers/WorkerFeature.h?rev=8dcf83e85d98#38
Should we morph this into the budget or timeout ideas?
Sure, why not.
Summary: crash in shutdownhang | ntdll.dll@0xa5154 | Hang in Sync XHR from unload on shutdown. → Abort network loads on shutdown to prevent hangs in sync XHR from unload
You need to log in before you can comment on or make changes to this bug.