Closed
Bug 1755375
Opened 3 years ago
Closed 3 years ago
GPU process kills are registered as crashes.
Categories
(GeckoView :: Sandboxing, defect)
Tracking
(firefox99 fixed)
RESOLVED
FIXED
99 Branch
Tracking | Status | |
---|---|---|
firefox99 | --- | fixed |
People
(Reporter: agi, Assigned: jnicol)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
When the GPU process is killed by the OS, we should not start the crashreporter.
You can reproduce this by calling adb shell kill -9 <gpu process PID>
when the browser is in the background.
Assignee | ||
Comment 1•3 years ago
|
||
If the android system kills the GPU process then ChildCrashHandler.jsm
gets invoked but an empty dump ID. Currently we generate a crash
report anyway, which is resulting in lots of "EMPTY: no crashing
thread identified; ERROR_NO_MINIDUMP_HEADER" crashes.
Instead, we should return early before starting the crash reporter if
the dump ID is empty. We already do this for content processes, so
this patch makes us do so for every type of process.
Updated•3 years ago
|
Assignee: nobody → jnicol
Status: NEW → ASSIGNED
Pushed by jnicol@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0fae6a6b254a
Don't generate crash reports when android kills the GPU process. r=agi
Comment 3•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox99:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
Comment 4•2 years ago
|
||
Moving GPU process bugs to the new GeckoView::Sandboxing component.
Component: General → Sandboxing
You need to log in
before you can comment on or make changes to this bug.
Description
•