Open Bug 1493232 Opened 6 years ago Updated 1 year ago

The GeckoView crash reporter fails to be triggered by native crashes not in Gecko

Categories

(GeckoView :: General, defect, P3)

Product:
GeckoView
Component:
General
Type:
defect

Tracking

(firefox63 wontfix, firefox64 wontfix, firefox65 affected)

Tracking Flags:
Tracking Status
firefox63 --- wontfix
firefox64 --- wontfix
firefox65 --- affected

People

(Reporter: rbarker, Unassigned)

Details

On both HTC Wave and Oculus Mobile platforms, the GeckoView crash reporter fails to be triggered by native crashes out side of Gecko. In Firefox Reality, there is a render thread that is not part of Gecko. Any crashes in that thread fail to trigger the crash reporter on both platforms. On Google's Daydream platform the crash reporter does get triggered by crashes in the external render loop.
Whiteboard: [geckoview:fxr:p1]
Summary: The GeckoView crash reporter fails to be trigger by native crashes no in Gecko → The GeckoView crash reporter fails to be triggered by native crashes not in Gecko
Assignee: nobody → rbarker
63=wontfix because FxR 1.1 will ship GV 64.
status-firefox63: --- → wontfix
Randall's waiting for his new Linux dev machine to debug this issue.
Product: Firefox for Android → GeckoView
Assignee: rbarker → nobody

I'm editing a bunch of GeckoView bugs. If you'd like to filter all this bugmail, search and destroy emails containing this UUID:

e88a5094-0fc0-4b7c-b7c5-aef00a11dbc9

Priority: P1 → P2
Rank: 15
Whiteboard: [geckoview:fxr:p1]
Priority: P2 → P3
Severity: normal → S3
Rank: 15 → 333
You need to log in before you can comment on or make changes to this bug.