Closed Bug 1755375 Opened 3 years ago Closed 3 years ago

GPU process kills are registered as crashes.

Categories

(GeckoView Graveyard :: Sandboxing, defect)

Unspecified
All
defect

Tracking

(firefox99 fixed)

RESOLVED FIXED
99 Branch
Tracking Status
firefox99 --- fixed

People

(Reporter: agi, Assigned: jnicol)

References

Details

Attachments

(1 file)

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.

Blocks: 1331109

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.

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
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch

Moving GPU process bugs to the new GeckoView::Sandboxing component.

Component: General → Sandboxing
Product: GeckoView → GeckoView Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: