Closed Bug 1594734 Opened 2 years ago Closed 2 years ago

Crash in [@ malformed]

Categories

(GeckoView :: General, defect)

72 Branch
Unspecified
Android
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED MOVED

People

(Reporter: marcia, Unassigned)

References

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-db8c63a6-5e31-49a2-b3bf-4c91b0191107.

Seen while looking at Fenix nightly crash stats: https://bit.ly/2CoIfEh. This may have already been addressed, but it did accumulate a large number of crashes in the last 7 days - 19770 crashes/3193 installs. This was also flagged as a startup crash.

Java stack trace:

java.lang.RuntimeException: Error receiving broadcast Intent { act=mozilla.components.feature.downloads.OPEN flg=0x10 pkg=org.mozilla.fenix.nightly (has extras) } in mozilla.components.feature.downloads.AbstractFetchDownloadService$broadcastReceiver$2$1@c47220e
	at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1401)
	at android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA.run(Unknown Source:2)
	at android.os.Handler.handleCallback(Handler.java:873)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:193)
	at android.app.ActivityThread.main(ActivityThread.java:6718)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Caused by: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=content://org.mozilla.fenix.nightly.fileprovider/Download/Download/null typ=application/zip flg=0x10000001 }
	at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2007)
	at android.app.Instrumentation.execStartActivity(Instrumentation.java:1673)
	at android.app.ContextImpl.startActivity(ContextImpl.java:917)
	at android.app.ContextImpl.startActivity(ContextImpl.java:888)
	at android.content.ContextWrapper.startActivity(ContextWrapper.java:379)
	at mozilla.components.feature.downloads.AbstractFetchDownloadService$broadcastReceiver$2$1.onReceive(AbstractFetchDownloadService.kt:34)
	at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1391)

cpeterson - Not sure if this is related to some of the issues we had recently that were filed in Github, but because of the volume I decided to file it.

Flags: needinfo?(cpeterson)

James says this is a Fenix bug. Also Fenix's crash reporter is not supposed to be submitting Java crash reports to Socorro, just native code crashes.

I think this is Fenix bug https://github.com/mozilla-mobile/fenix/issues/6436 ("RuntimeException: Error receiving broadcast Intent { act=mozilla.components.feature.downloads.OPEN") caused by incomplete file downloads bug 1594905.

Depends on: 1594905
Flags: needinfo?(cpeterson)

@ Sebastian, James was surprised that we have Java exception reports from Fenix in Socorro. Does Fenix's crash reporter submit both native code crash reports and Java exception reports to both Socorro and Sentry? James thought Fenix's crash reporter only submitted native code crashes to Socorro.

Flags: needinfo?(s.kaspari)
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → MOVED

Yes, we started sending all crash reports to Socorro in order to get a better understanding of the app quality. Sentry is not really helpful except for looking at individual crashes, telemetry only collects crash counts at the moment and Google play statistics may be something we will not be able to use going forward. Since crash-stats worked for Fennec, we wanted to see if that will work for Fenix too. Is this okay or will that cause issues for your processes?

Flags: needinfo?(s.kaspari)

(In reply to Sebastian Kaspari (:sebastian; :pocmo) from comment #4)

Is this okay or will that cause issues for your processes?

👍 Yes, this is okay. It was just a surprise.

You need to log in before you can comment on or make changes to this bug.