Ensure content processes cannot shutdown during async process switches
Categories
(Core :: DOM: Content Processes, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
Details
Attachments
(4 files)
I think it is possible right now for a shutdown message to be sent to a content process between the time when CanonicalBrowsingContext
begins async process launching, and when the process is actually used to create a new BrowserParent
.
This bug tracks adding some mechanism to prevent the process from shutting down during that time.
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Comment 5•5 years ago
|
||
Backed out 3 changesets for causing failures in test_multiple_nav_process_switches.
Backout link: https://hg.mozilla.org/integration/autoland/rev/2799d2f79290ca6a9d7982f9eeb3640dccf8b08e
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=306682786&repo=autoland&lineNumber=13897
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Comment 8•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1a4de0e50652
https://hg.mozilla.org/mozilla-central/rev/20252e44605a
https://hg.mozilla.org/mozilla-central/rev/b21844a2bdeb
https://hg.mozilla.org/mozilla-central/rev/f2d3b3bb9261
Description
•