Crash in [@ java.lang.RuntimeException: at mozilla.components.browser.engine.gecko.GeckoEngine$$ExternalSyntheticLambda36.onShutdown(R8$$SyntheticClass:5)]
Categories
(GeckoView :: General, defect, P1)
Tracking
(firefox139+ wontfix, firefox140+ affected, firefox141+ affected)
People
(Reporter: cpeterson, Assigned: owlish, NeedInfo)
References
(Depends on 1 open bug)
Details
(4 keywords)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/a442400c-821f-491c-8a61-1bb8b0250529
This crash looks like a regression, or the crash signature changed, in 138.
Exception: java.lang.RuntimeException
Message: GeckoRuntime is shutting down
Top 10 frames:
0 mozilla.components.browser.engine.gecko.GeckoEngine$$ExternalSyntheticLambda36 onShutdown R8$$SyntheticClass:5
1 org.mozilla.geckoview.GeckoRuntime$1 handleMessage GeckoRuntime.java:31
2 org.mozilla.gecko.EventDispatcher$3 run EventDispatcher.java:13
3 android.os.Handler handleCallback Handler.java:873
4 android.os.Handler dispatchMessage Handler.java:99
5 android.os.Looper loop Looper.java:193
6 android.app.ActivityThread main ActivityThread.java:6782
7 java.lang.reflect.Method invoke Method.java:-2
8 com.android.internal.os.RuntimeInit$MethodAndArgsCaller run RuntimeInit.java:493
9 com.android.internal.os.ZygoteInit main ZygoteInit.java:868
Assignee | ||
Updated•20 days ago
|
Updated•20 days ago
|
Comment 1•19 days ago
|
||
Hey Ted, thanks for adding all the other signatures. It looks like it's not a new crash then. Do you recommend leaving high severity S1 or lowering it?
Updated•19 days ago
|
Comment 2•19 days ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 AArch64 and ARM crashes on release
For more information, please visit BugBot documentation.
Comment 3•19 days ago
|
||
The bug is marked as tracked for firefox140 (beta) and tracked for firefox141 (nightly). However, the bug still isn't assigned.
:owlish, 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.
Updated•19 days ago
|
Updated•19 days ago
|
Comment 4•13 days ago
|
||
This is a reminder regarding comment #3!
The bug is marked as tracked for firefox139 (release), tracked for firefox140 (beta) and tracked for firefox141 (nightly). We have limited time to fix this, the soft freeze is in 14 days. However, the bug still isn't assigned.
Comment 5•11 days ago
|
||
Too late to fix for 139 at this point, but this feels like something that we shouldn't let fall off the radar.
Updated•8 days ago
|
Comment 6•7 days ago
|
||
This is a reminder regarding comment #3!
The bug is marked as tracked for firefox140 (beta) and tracked for firefox141 (nightly). We have limited time to fix this, the soft freeze is in 8 days. However, the bug still isn't assigned.
Assignee | ||
Updated•6 days ago
|
Assignee | ||
Comment 7•6 days ago
•
|
||
These stack traces are not helpful because they do not provide any reason for the crush. Resolving bug 1872429 might help us get more visibility
Updated•2 days ago
|
Description
•