Closed Bug 1832564 Opened 2 years ago Closed 2 years ago

Crash in [@ java.lang.RuntimeException: at org.mozilla.fenix.settings.SyncDebugFragment$$ExternalSyntheticLambda3.onShutdown(R8$$SyntheticClass:5)]

Categories

(Firefox for Android :: Accounts and Sync, defect, P3)

Product:
Firefox for Android
Component:
Accounts and Sync
Platform:
Unspecified
Android
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox113 --- wontfix
firefox114 --- fixed
firefox115 --- fixed
firefox116 --- fixed

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: crash, regression, topcrash, Whiteboard: [fxdroid])

Crash Data

New crash in v113, currently the #14 overall topcrash.

Crash report: https://crash-stats.mozilla.org/report/index/c2e5539a-0e3c-4620-8fa2-e81840230511

Java stack trace:

java.lang.RuntimeException
	at org.mozilla.fenix.settings.SyncDebugFragment$$ExternalSyntheticLambda3.onShutdown(R8$$SyntheticClass:5)
	at org.mozilla.geckoview.GeckoRuntime$1.handleMessage(GeckoRuntime.java:31)
	at org.mozilla.gecko.EventDispatcher$3.run(EventDispatcher.java:13)
	at android.os.Handler.handleCallback(Handler.java:794)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:173)
	at android.app.ActivityThread.main(ActivityThread.java:6651)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:822)

This looks like a regression in Fenix 112.

Crash Signature: [@ java.lang.RuntimeException: at org.mozilla.fenix.settings.SyncDebugFragment$$ExternalSyntheticLambda3.onShutdown(R8$$SyntheticClass:5)] → [@ java.lang.RuntimeException: at org.mozilla.fenix.settings.SyncDebugFragment$$ExternalSyntheticLambda1.onShutdown(R8$$SyntheticClass:5)] [@ java.lang.RuntimeException: at org.mozilla.fenix.settings.SyncDebugFragment$$ExternalSyntheticLambda2.onShutdown…
status-firefox114: --- → ?
status-firefox115: --- → ?

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

  • Top 10 AArch64 and ARM crashes on beta

For more information, please visit BugBot documentation.

Keywords: topcrash
Flags: needinfo?(jmahon)

We might be able to get this into the final dot release (if this gets landed EOW this week) otherwise this will have to get punted to release in 114.

Marking as P1 specifically because we don't have a great handle on what's crashing & whether this is leading to other crash reports that aren't captured by this stack trace.

Severity: -- → S2
Flags: needinfo?(jmahon)
Priority: -- → P1
Whiteboard: [fxdroid]

Not seeing any variants of this signature affecting 114 or 115 yet.

Still no crashes from 114+. We can probably close this as WFM after 114 goes to Release if that continues. Setting the status to affected for now just for visibility.

status-firefox113: affected → wontfix
status-firefox114: ? → affected
status-firefox114: affected → ?
Priority: P1 → P3

We've received at least two reports from 115.0a1, but still none from 114.

https://crash-stats.mozilla.org/report/index/84c4c1d9-e56e-477a-9046-465000230528

status-firefox115: ? → affected

Resolving as WFM - not seeing any crash reports in 114 or 115

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox114: ? → fixed
status-firefox115: affected → fixed
status-firefox116: --- → fixed
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.