Open Bug 1543688 Opened 1 year ago Updated 1 year ago

Crash in [@ java.lang.OutOfMemoryError]

Categories

(Firefox for Android :: General, defect, P2)

Unspecified
Android
defect

Tracking

()

Tracking Status
firefox-esr68 --- affected
firefox66 --- wontfix
firefox67 --- fix-optional
firefox68 --- wontfix
firefox69 --- ?

People

(Reporter: marcia, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-c1553ffa-c591-48e9-a12e-4274b0190411.

Seen while looking at release crash stats: https://bit.ly/2Z4qQL9. This crash accumulates a pretty consistent number of crashes per release. Some of the comments mention repeatedly crashing, sometimes every 15 seconds. Currently on 66.0.2 this is #28 overall.

High correlation to Samsung devices - (62.61% in signature vs 38.16% overall) android_brand = samsung

The reporter in Bug 1543262 listed this as one of his crashes and notes in that bug that Fennec is unusable (He is checking out whether uBlock might be to blame)

Java stack trace:

java.lang.OutOfMemoryError

No crash at all on 67 and 68, the signature may have changed. I am marking it as wontfix for 67 to remove it from our triaging queues for 67.

The spike on 66.0.2 without any crashes in beta makes me think this could be some kind of compiler/build issue.

Priority: -- → P2

Currently #10 overall in 68.0b5.

Crash volume is down now in beta 13/14. But we don't know why.

Over 5600 crashes in Fennec 68 release. Comments are not particularly useful.

Some correlations:

*(33.02% in signature vs 05.83% overall) android_version = 24 (REL)
*(24.37% in signature vs 05.29% overall) android_version = 23 (REL)
*Adreno (TM) 330, 2378 crashes in 6 months
*APIs range from 29-21

Downgrading from priority P1 to P2.

Priority: P1 → P2
You need to log in before you can comment on or make changes to this bug.