1918633 - Crash in [@ CrashReporterUnableToRestoreException(message=Missing ThrowableData): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run.(RuntimeInit.java)]

Status: RESOLVED WORKSFORME

(Firefox for Android :: Crash Reporting, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

These Nightly 132.0a1 crashes started after bug 1910490 landed.

Crash report: https://crash-stats.mozilla.org/report/index/0734cd27-422e-4f7b-a864-5ce6e0240913

Top 10 frames:

0  com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run  ?  RuntimeInit.java:562
1  com.android.internal.os.ZygoteInit.main  ?  ZygoteInit.java:977
2  com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run  ?  RuntimeInit.java:552
3  mozilla.components.support.base.android.NotificationsDelegate.requestNotifica...  ?  NotificationsDelegate.kt:125
4  mozilla.components.support.base.android.NotificationsDelegate.notify$default  ?  NotificationsDelegate.kt:68
5  org.mozilla.fenix.FenixApplication$initializeWebExtensionSupport$2.invoke  ?  FenixApplication.kt:542
6  mozilla.components.browser.engine.gecko.GeckoEngine$registerWebExtensionDeleg...  ?  GeckoEngine.kt:63
7  org.mozilla.geckoview.WebExtensionController.updatePrompt  ?  WebExtensionController.java:75
8  org.mozilla.geckoview.WebExtensionController.handleMessage  ?  WebExtensionController.java:26
9  org.mozilla.geckoview.WebExtensionController$Internals.handleMessage  ?  WebExtensionController.java:4

Comment 1

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Are these old crash reports? There are crash reports for bug 1910114 which is a crash which affected Fenix Nightly in Late July. Do Fenix crash reports use the application information like build ID of the submitting Fenix version instead of the one which hit the crashing code?

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The bug is marked as tracked for firefox132 (nightly). We have limited time to fix this, the soft freeze is in 13 days. However, the bug still isn't assigned.

:royang, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Comment 3

[Roger Yang [:royang]]

:jboek, I'll let you decides what to do with this? Thanks

Comment 4

[Andrew McCreight [:mccr8]]

There's literally about another 30 different CrashReporterUnableToRestoreException signatures looking at the last week of Android 132.0a1 crashes. Thousands upon thousands of crashes, with something like 100 per install time.

Comment 5

[Jeff Boek [:boek]]

These most likely old crash reports that were never sent. I created Bug 1918748 and Bug 1918747 to follow up with these. I will add a patch to disable the new reporter in Nightly until these two land

Comment 6

[Jeff Boek [:boek]]

Logged Bug 1918750 to disable it in Nightly.

Comment 7

[Ryan VanderMeulen [:RyanVM]]

As expected, new submissions are going away now.

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

The bug is linked to topcrash signatures, which match the following criterion:

• Top 10 AArch64 and ARM crashes on nightly

For more information, please visit BugBot documentation.

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:royang, could you have a look please?

For more information, please visit BugBot documentation.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.

For more information, please visit BugBot documentation.

Comment 11

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.