1968016 - startup Crash in [@ java.lang.RuntimeException: at android.app.ActivityThread.handleBindApplication(ActivityThread.java)]

Status: RESOLVED FIXED

(Firefox for Android :: Experimentation and Telemetry, defect)

Description

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

60-130 crashes per Firefox for Android Beta of the 139 branch, mostly lower API versions (21-28).

Crash report: https://crash-stats.mozilla.org/report/index/92188383-1fcd-4f65-82f3-913650250522

Top 10 frames:

0  org.mozilla.experiments.nimbus.internal.NimbusKt  access$uniffiCheckCallStatus  nimbus.kt:69
1  org.mozilla.fenix.components.NimbusComponents$$ExternalSyntheticLambda0  invoke  R8$$SyntheticClass:368
2  kotlin.SynchronizedLazyImpl  getValue  LazyJVM.kt:21
3  org.mozilla.fenix.components.NimbusComponents  getSdk  NimbusComponents.kt:3
4  org.mozilla.fenix.FenixApplication  onCreate  FenixApplication.kt:124
5  android.app.Instrumentation  callApplicationOnCreate  Instrumentation.java:1013
6  android.app.ActivityThread  handleBindApplication  ActivityThread.java:4712
7  android.app.ActivityThread  -wrap1  ActivityThread.java:-1
8  android.app.ActivityThread$H  handleMessage  ActivityThread.java:1405
9  android.os.Handler  dispatchMessage  Handler.java:102

Comment 1

[Ryan VanderMeulen (PTO, back 6-April)]

Not entirely sure who to ping on this one, but starting with Ben because of the uniffi code on the stack.

Comment 2

[Ben Dean-Kawamura [:bdk]]

I don't have much insight into this, but here's what I can figure out:

• The UniFFI issue is InternalException which is only thrown if something very wrong happens. For example, an invalid status code is sent over the FFI. There doesn't seem to be much more information than that.
• When I click on the reports tab, about half the issues seem to be UniFFI and the other half seem to be Glean.
• I also see reports from 138 and 140. Not sure what the breakdown is between the 3.

At this point, I want to say this is just old phones being flakey and I don't think we necessarily need to look into it more. If we wanted to dig deeper, is there a way to get the InternalException messages? Those would help narrow this down.

Comment 3

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

The bug is linked to a topcrash signature, which matches the following criteria:

• Top 10 AArch64 and ARM crashes on nightly
• Top 10 AArch64 and ARM crashes on beta

For more information, please visit BugBot documentation.

Comment 4

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

The bug is marked as tracked for firefox139 (beta) and tracked for firefox140 (nightly). However, the bug still isn't assigned.

:towhite, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Comment 5

[Ryan VanderMeulen (PTO, back 6-April)]

The volume on this crash also appears to be dropping since we reverted JNA and shipped 139.0 RC3. Looks like this spike may have been the Fenix version of bug 1968018.

Comment 6

[Ryan VanderMeulen (PTO, back 6-April)]

This signature is a bit generic, but the API 21-23 spike clearly seems to be resolved by the blocking bugs.