Closed
Bug 1634097
Opened 4 years ago
Closed 4 years ago
Gecko must not automatically restart killed content processes on Android
Categories
(GeckoView Graveyard :: Sandboxing, defect, P1)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bugzilla, Unassigned)
References
Details
If the kill was initiated by the OS, then it is probably due to resource constraints. We don't want to be fighting that.
Hopefully this is just a pref flip or something. If not, I'll move this to DOM.
|
Reporter | |
Updated•4 years ago
|
Summary: Gecko must not automatically restarted killed content processes on Android → Gecko must not automatically restart killed content processes on Android
|
|
Reporter | |
Comment 1•4 years ago
|
||
I think this might be a false alarm, modulo another bug that I found. I'll keep this open for testing to confirm that, but I don't think we need to do anything here.
We don't believe content processes are currently being automatically restarted. Closing.
Status: NEW → RESOLVED
Closed: 4 years ago
Priority: -- → P1
Resolution: --- → WORKSFORME
|
||
Comment 3•2 years ago
|
||
Moving content process management bugs to the new GeckoView::Sandboxing component.
Component: General → Sandboxing
|
||
Updated•4 months ago
|
Product: GeckoView → GeckoView Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•