Closed Bug 1646088 Opened 5 years ago Closed 5 years ago

Ensure content processes cannot shutdown during async process switches

Categories

(Core :: DOM: Content Processes, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla79
Fission Milestone M6a
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.

Pushed by nlayzell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/77d15266af3c Part 1: Keep processes alive during process switches, r=kmag https://hg.mozilla.org/integration/autoland/rev/ef746bdcbaf6 Part 2: Create ScriptableCPInfo in the constructor, r=kmag https://hg.mozilla.org/integration/autoland/rev/8c4a24b91c88 Part 3: Add a test for slow process switches, r=kmag
Flags: needinfo?(nika)
Pushed by nlayzell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1a4de0e50652 Part 1: Keep processes alive during process switches, r=kmag https://hg.mozilla.org/integration/autoland/rev/20252e44605a Part 2: Create ScriptableCPInfo in the constructor, r=kmag https://hg.mozilla.org/integration/autoland/rev/b21844a2bdeb Part 3: Add a test for slow process switches, r=kmag https://hg.mozilla.org/integration/autoland/rev/f2d3b3bb9261 Part 4: Update browser_httpCrossOriginOpenerPolicy for keeping processes alive during switches, r=valentin
Regressions: 1647624
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: