Closed
Bug 1705724
Opened 4 years ago
Closed 4 years ago
Figure out if there's a reasonable way to handle content process crashes mid-load
Categories
(Core :: DOM: Content Processes, defect, P3)
Core
DOM: Content Processes
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: emilio, Unassigned)
References
Details
Bug 1704651 fixed a leak when a tab opened by Client.openWindow
is closed mid-load.
There's a more general version of that kind of leak if the content process crashes. It's not clear to me what's the best way to potentially handle that kind of thing, but it seems something worth trying to figure out.
Reporter | ||
Updated•4 years ago
|
Updated•4 years ago
|
Priority: -- → P3
Updated•4 years ago
|
Severity: -- → S3
Comment 1•4 years ago
|
||
This might be fixed by your changes in https://phabricator.services.mozilla.com/D112419, as that will synthesize the STATE_STOP
notification for us. Can we close this one now?
Flags: needinfo?(emilio)
Reporter | ||
Comment 2•4 years ago
|
||
Yeah guess so. At least I don't have any more concrete suggestions.
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(emilio)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•