Closed Bug 1690356 Opened 4 years ago Closed 4 years ago

Crash in [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER]

Categories

(GeckoView :: General, defect)

Unspecified
Android
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1644486

People

(Reporter: furkan, Unassigned)

Details

(Keywords: crash)

Crash Data

Maybe Fission related. (DOMFissionEnabled=1)

Crash report: https://crash-stats.mozilla.org/report/index/d0cfe339-b916-4342-9401-e3bbf0210202

Component: General → DOM: Content Processes
Product: Firefox → Core

This is not Fission related, as these crashes are also seen on Beta, ESR and Fenix, where Fission enablement is not possible.

92% (~60k) of these crashes in the last 7 days are on Fenix. Someone from the Fenix team and/or the crash reporter should look into this, and figure out why we land in this scenario and what we can do to fix this.

Component: DOM: Content Processes → Stability
Product: Core → Fenix
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: crash
OS: Unspecified → Android

Sending this over to the GV team as this component is only for issues that are tracked in GitHub. Aaron is the most knowledgeable person here. AFIK we have not shipped Fission to any release users so this might be a case of pref flipping or some third party fork shipping bad state?

Component: Stability → General
Flags: needinfo?(aklotz)
Product: Fenix → GeckoView

We already have bug 1644486 for this signature in general; as for Fission, nobody should be using that, so it's probably a case of somebody expecting to be able to set Desktop prefs on mobile.

Flags: needinfo?(aklotz)

Lets close as a duplicate of that.

Looking at comment 0 it has nothing to do with Fenix so I don't quite understand how this got directed mobile's way.

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