Closed Bug 1542410 Opened 6 years ago Closed 6 years ago

Loading about:telemetry's Raw JSON data will hang Fenix, even after restarting the app

Categories

(GeckoView :: General, defect, P1)

All
Android
defect

Tracking

(firefox66 wontfix, firefox67 wontfix, firefox68 affected)

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

People

(Reporter: cpeterson, Unassigned)

References

Details

(Whiteboard: [geckoview:fenix:m4])

STR:

  1. In Fenix, load about:telemetry.
  2. Click the "Raw JSON" link.
  3. Before the JSON finishes loading, press the Android Back button.

EXPECTED RESULT:
In Fennec and Focus+GV, the JSON data is loaded in the browser or you are given the open to open in a JSON Viewer app.

ACTUAL RESULT:
Fenix hangs while trying to load the JSON data.

If I kill the Fenix process and launch it again, Fenix will still hang. Perhaps the Fenix home screen is trying to show the JSON data in the list of recent sessions? I had to uninstall and reinstall Fenix to make it stop hanging.

I don't see a "Raw JSON" link.. did that get removed?

Flags: needinfo?(cpeterson)

(In reply to David Bolter [:davidb] (NeedInfo me for attention) from comment #1)

I don't see a "Raw JSON" link.. did that get removed?

I still see "Raw JSON" at the bottom of the left column. It's a small text link beneath "Keyed Scalars".

I just reproduced the perma-hang (on my Moto G5) and now must uninstall/reinstall Fenix.

Flags: needinfo?(cpeterson)

I reproduced this on a pixel 2. A few observations:

  • You don't need to uninstall/reinstall Fenix to get unstuck, you can just clear the application data.
  • This worked fine on the relatively-recent Fenix build I had installed, but I got the hang after upgrading. So this is a recent regression.
  • It's not actually a hang, just a very long period of jank. It recovers (and displays the JSON as text) in about 2.5 minutes.
  • I took a profile: https://perfht.ml/2XlrsdH . The Gecko threads in the parent and content processes seem idle and responsive.
  • The hang doesn't actually require visiting the page, just putting the extremely-long data URI in the URL bar is sufficient. As such, I'm pretty sure the bug involves some exponential URL text processing in Fenix.

James says this is a Fenix issue. They shouldn't break long URLs.

I filed a Fenix issue: https://github.com/mozilla-mobile/fenix/issues/1824

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.