Crash doesn't get sent or doesn't show in about:crashes

NEW
Unassigned

Status

()

Firefox for Android
General
--
critical
2 years ago
a year ago

People

(Reporter: Usul, Unassigned)

Tracking

({crash})

Trunk
crash
Points:
---

Firefox Tracking Flags

(firefox50 affected)

Details

(URL)

Attachments

(2 attachments)

(Reporter)

Description

2 years ago
Created attachment 8774031 [details]
Adb logcat capture of the crash

I found an url which let's me crash , I see the crash report dialog, but the crash never shows up in about:crashes.

I've managed to capture the crash in adb logcat (attached).

Str :
1) load http://mobile.lemonde.fr/europe/article/2016/07/22/coups-de-feu-dans-un-centre-commercial-a-munich-en-allemagne_4973622_3214.html
2) wait a bit and while article isn't completely loaded start reading scrolling.
(Reporter)

Updated

2 years ago
Severity: normal → critical
If you submitted crash reports with an email address you can log into crash stats to view recent crashes at https://crash-stats.mozilla.com/profile/

From the logcat I see

E/GeckoCrashReporter(20623): exception while reading strings: 
E/GeckoCrashReporter(20623): java.lang.ArrayIndexOutOfBoundsException: index=1
E/GeckoCrashReporter(20623): 	at java.util.regex.Matcher.appendEvaluated(Matcher.java:149)
E/GeckoCrashReporter(20623): 	at java.util.regex.Matcher.appendReplacement(Matcher.java:111)
E/GeckoCrashReporter(20623): 	at java.util.regex.Matcher.replaceAll(Matcher.java:321)
E/GeckoCrashReporter(20623): 	at java.lang.String.replaceAll(String.java:1785)
E/GeckoCrashReporter(20623): 	at org.mozilla.gecko.CrashReporter.readStringsFromReader(CrashReporter.java:286)
E/GeckoCrashReporter(20623): 	at org.mozilla.gecko.CrashReporter.readStringsFromFile(CrashReporter.java:273)
E/GeckoCrashReporter(20623): 	at org.mozilla.gecko.CrashReporter.onCreate(CrashReporter.java:142)
E/GeckoCrashReporter(20623): 	at android.app.Activity.performCreate(Activity.java:5312)
E/GeckoCrashReporter(20623): 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1111)
E/GeckoCrashReporter(20623): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2541)
E/GeckoCrashReporter(20623): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2641)
E/GeckoCrashReporter(20623): 	at android.app.ActivityThread.access$800(ActivityThread.java:156)
E/GeckoCrashReporter(20623): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1355)
E/GeckoCrashReporter(20623): 	at android.os.Handler.dispatchMessage(Handler.java:102)
E/GeckoCrashReporter(20623): 	at android.os.Looper.loop(Looper.java:157)
E/GeckoCrashReporter(20623): 	at android.app.ActivityThread.main(ActivityThread.java:5867)
E/GeckoCrashReporter(20623): 	at java.lang.reflect.Method.invokeNative(Native Method)
E/GeckoCrashReporter(20623): 	at java.lang.reflect.Method.invoke(Method.java:515)
E/GeckoCrashReporter(20623): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858)
E/GeckoCrashReporter(20623): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:674)
E/GeckoCrashReporter(20623): 	at dalvik.system.NativeStart.main(Native Method)
(Reporter)

Comment 2

2 years ago
(In reply to Kevin Brosnan [:kbrosnan] from comment #1)
> If you submitted crash reports with an email address you can log into crash
> stats to view recent crashes at https://crash-stats.mozilla.com/profile/

They don't show up in crash stats either I only see my desktops crashes while logged in.

Comment 3

2 years ago
This happens to me too. Annoying since I'm trying to figure out a crash that only seems to happen on some devices.

Seen on a stock Samsung S6 with Android 6.0.1.

Comment 4

2 years ago
Tried it on a different S6 with the same version of Android. The crash still happened there, but it managed to submit something at least:

https://crash-stats.mozilla.com/report/index/8e31a13f-768d-4b1b-8e6b-b0cf02160831
(Reporter)

Comment 5

2 years ago
Created attachment 8788078 [details]
Another crash while scrolling
You need to log in before you can comment on or make changes to this bug.