Closed
Bug 1101257
Opened 10 years ago
Closed 10 years ago
[e10s] Possible hang with CPOWs, nested event loop
Categories
(Core :: DOM: Content Processes, defect)
Core
DOM: Content Processes
Tracking
()
RESOLVED
DUPLICATE
of bug 567058
Tracking | Status | |
---|---|---|
e10s | m5+ | --- |
People
(Reporter: billm, Assigned: billm)
References
Details
So far this is just a theoretical problem. I'm not sure if it can actually happen.
1. Content process sends an intr message.
2. While waiting for the response, content process dispatches some incoming messages.
3. Parent process sends a CPOW.
4. Content process receives the CPOW and doesn't post the OnMaybeDequeueOne task because AwaitingInterruptReply() is true.
5. Content process, while still dispatching an incoming message, enters a nested event loop (for an alert(), say).
The parent won't do anything at this point because it's waiting for the CPOW reply. The child is also stuck because there's nothing to compel it to dispatch the CPOW.
I've gotten a lot of hangs lately (maybe once every day or two) where the parent is waiting for a CPOW response and the child is in a nested event loop for nsPrompter.js. It seems possible that this could be the cause. Bug 641685 recently added a new source of intr messages in PContent, so the timeline kinda fits.
Updated•10 years ago
|
Assignee: nobody → wmccloskey
tracking-e10s:
--- → m5+
Assignee | ||
Comment 1•10 years ago
|
||
This was fixed by bug 567058.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•