If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[e10s] Child process crash when closing tab immediately after opening

NEW
Assigned to

Status

()

Core
DOM: Content Processes
P3
critical
3 years ago
a year ago

People

(Reporter: mossop, Assigned: bjacob)

Tracking

(Blocks: 1 bug, {crash})

unspecified
x86
Mac OS X
crash
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(e10s+)

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8480246 [details]
log

An automated test I am working on does the following:

Load a page in a tab.
Click a link in the page which will trigger a new tab to open.
Wait for the TabOpen event.
Close the new tab immediately.

Randomly this will cause the child process to crash because the TabParent has been destroyed before the TabChild has finished initialising, specifically creating the PRenderFrame.

Attached is a log showing this happening, I added some additional logs to TabParent calls, you can see that TabParent 0x11d337c00 is created then later destroyed and its mOwnerElement nulled out. Later the child calls AllocPRenderFrameParent which fails because there is no longer a frameloader.

I can fix the test by having it wait for the tab to load before closing but I suspect this might be a common thing in browser-chrome tests so it might be a good idea to fix this.
(Assignee)

Updated

3 years ago
Assignee: nobody → bjacob
tracking-e10s: ? → +
(Assignee)

Updated

3 years ago
Blocks: 984139
Blocks: 1006043
Severity: normal → critical
Keywords: crash
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.