This bug was filed from the Socorro interface and is report bp-5600dbf5-dc3c-4111-a749-043da2161215. ============================================================= Mfg. Model And. API CPU ABI # samsung SM-G920F 23 (REL) armeabi-v7a 1021 34.6% samsung SM-G925F 23 (REL) armeabi-v7a 624 21.1% samsung SAMSUNG-SM-G920A 23 (REL) armeabi-v7a 190 6.4% samsung SM-G920W8 23 (REL) armeabi-v7a 114 3.9% samsung SM-G920V 23 (REL) armeabi-v7a 110 3.7%
Track 51+ as crash in 51. Hi :jorendorff, Can you help shed some light here or find an owner for this?
tracking-firefox51: ? → +
I don't see this particular signature in 52 or 53, so I think we have to recheck whether those branches are affected.
Android has 8k users on Aurora and 1k users on Nightly. We may not have the right mix of users on to see it.
Mark 51 fix-optional as the number is getting low in recent builds in crash report.
status-firefox51: affected → fix-optional
Not super high volume at this point, but we should keep an eye on this for 52 release.
status-firefox52: affected → fix-optional
This is likely to be fixed by the dalvik-main space bug. See bug 1323351 comment 6 and 7 along with the meta bug that this bug is linked to.
I'm dropping tracking here but asking for help in related bugs and the meta bug.
tracking-firefox53: + → -
GC crash, characteristically hard to act on. Way down from 57 to 58 but not gone. The method still exists.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.