Open Bug 1541152 Opened 5 years ago Updated 1 year ago

Disable GV's about:crashes

Categories

(GeckoView :: General, defect, P3)

All
Android

Tracking

(firefox66 wontfix, firefox67 wontfix, firefox68 affected)

Tracking Status
firefox66 --- wontfix
firefox67 --- wontfix
firefox68 --- affected

People

(Reporter: cpeterson, Unassigned)

References

Details

This issue was originally reported in the Fenix issue tracker:
https://github.com/mozilla-mobile/fenix/issues/1221

Since GV delegates crash reporting to the app, GV's about:crashes doesn't show any crash reports. To avoid user confusion, GV should disable about:crashes. If the app wants to support about:crashes, it can write its own about:crashes handler and show the Socorro and Sentry crash reports it has caught and submitted.

Should we also disable about:telemetry? Fenix issue https://github.com/mozilla-mobile/fenix/issues/1347 says the about:telemetry page crashes GV.

Summary: Disable GV's about:crashes → Disable GV's about:crashes and about:telemetry

(In reply to Chris Peterson [:cpeterson] from comment #1)

Should we also disable about:telemetry? Fenix issue https://github.com/mozilla-mobile/fenix/issues/1347 says the about:telemetry page crashes GV.

Correction: we don't need to disable about:telemetry because it loads for me. However, GV's about:telemetry will only know about Gecko's telemetry probes. It won't know about any custom Fenix probes. The app side knows about all the Gecko telemetry, so perhaps the app should be responsible for about:telemetry so it can show both app and Gecko telemetry. (Just like the proposal for the app to be responsible for about:crashes so it can show both app and Gecko crash reports.)

Also, Fenix hung (once) when I tried to view the "Raw JSON" link (bug 1542410).

Priority: -- → P2
Summary: Disable GV's about:crashes and about:telemetry → Disable GV's about:crashes
Whiteboard: [geckoview:fenix:p2]
Rank: 25
Whiteboard: [geckoview:fenix:p2]
Priority: P2 → P3
Severity: normal → S3
Rank: 25 → 333
You need to log in before you can comment on or make changes to this bug.