Closed Bug 1185190 Opened 9 years ago Closed 9 years ago

[e10s] parent process hangs for several minutes after child process crashes

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1209689
Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: bugzilla.mozilla.org, Unassigned)

Details

When the child process crashes or is killed the parent process hangs (at 100% CPU on one core) for several minutes which makes it difficult to report child process crashes as it is easier to just kill the parent process to and restart firefox.

Stack of the busy thread via Process Explorer: http://pastebin.com/2XcGYFCm

I suspect this is due to the crash report tab getting loaded into every tab, even lazy background tabs that have never been touched after a session restore.
Do you see this anytime the content process crashes? Even with a single tab?

You can use this add-on to crash your content process: https://addons.mozilla.org/en-US/firefox/addon/tab-crasher/
Flags: needinfo?(bugzilla.mozilla.org)
> Do you see this anytime the content process crashes?

yes

> Even with a single tab?

with a single loaded tab? yes.

with just a single tab at all? no. hence my speculation that the child process crash report dialog is touching background tabs that it shouldn't.
Flags: needinfo?(bugzilla.mozilla.org)
I see. Yes, that seems like probably a good idea; to lazily load the about:tabcrashed state in each tab.
Blocks: e10s-perf
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.