Closed
Bug 1059564
Opened 10 years ago
Closed 3 years ago
[e10s] Child process crash when closing tab immediately after opening
Categories
(Core :: DOM: Content Processes, defect, P3)
Tracking
()
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: mossop, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Attachments
(1 file)
9.37 KB,
text/plain
|
Details |
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.
Updated•10 years ago
|
Assignee: nobody → bjacob
Updated•10 years ago
|
Blocks: e10s-tests
Updated•8 years ago
|
Priority: -- → P3
Comment 1•3 years ago
|
||
Hi Dave,
Is this issue still reproducible or it can be closed?
Thank you!
Flags: needinfo?(dtownsend)
Comment 3•3 years ago
|
||
There's no specific STR, so let's just close this.
Assignee: jacob.benoit.1 → nobody
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•