Crash in [@ java.lang.RuntimeException: at android.app.ActivityThread.performDestroyActivity(ActivityThread.java)]
Categories
(Fenix :: Onboarding, defect)
Tracking
(firefox127+ wontfix, firefox128+ wontfix, firefox129 fixed, firefox130 fixed)
People
(Reporter: aryx, Unassigned)
References
(Regression)
Details
(Keywords: crash, regression)
Crash Data
~280 crash reports from 210 installs for the last week, all Android versions affected
Crash report: https://crash-stats.mozilla.org/report/index/3312164a-fdc4-4fb6-b774-04b480240624
Top 10 frames:
0 android.view.WindowManagerGlobal findViewLocked WindowManagerGlobal.java:575
1 android.view.WindowManagerGlobal removeView WindowManagerGlobal.java:482
2 android.view.WindowManagerImpl removeViewImmediate WindowManagerImpl.java:216
3 mozilla.components.compose.cfr.CFRPopupFullscreenLayout dismiss$compose_cfr_release CFRPopupFullscreenLayout.kt:29
4 mozilla.components.compose.cfr.CFRPopup dismiss CFRPopup.kt:13
5 mozilla.components.compose.cfr.CFRPopupLayoutKt$CFRPopupLayout$1$invokeDismiss$1 invoke CFRPopupLayout.kt:23
6 mozilla.components.compose.cfr.CFRPopupLayoutKt$CFRPopupLayout$1$3$1 invoke CFRPopupLayout.kt:10
7 androidx.compose.ui.viewinterop.ViewFactoryHolder$releaseBlock$1 invoke AndroidView.android.kt:9
8 androidx.compose.ui.viewinterop.AndroidViewHolder onRelease AndroidViewHolder.android.kt:3
9 androidx.compose.ui.node.LayoutNode onRelease LayoutNode.kt:5
Reporter | ||
Comment 1•7 months ago
|
||
This crash signature existed before but got frequent with version 127.
Updated•7 months ago
|
Comment 2•7 months ago
|
||
:amejia could this be triaged and investigated?
It's too late for Fx127 but could follow in a Fx128 dot release
Comment 3•7 months ago
|
||
The bug is marked as tracked for firefox127 (release), tracked for firefox128 (beta) and tracked for firefox129 (nightly). We have limited time to fix this, the soft freeze is in 3 days. However, the bug still isn't assigned.
:amejia, 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 4•7 months ago
|
||
Tom, this crash looks like a regression from CFR bug 1891972. Bug 1893003 might be related, but it was resolved 2024-06-20 and we're still receiving these crash reports from more recent build IDs.
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Chris, from what I can see this appears to be fixed in Nightly?
Comment 6•7 months ago
|
||
(In reply to twhite from comment #5)
Chris, from what I can see this appears to be fixed in Nightly?
Indeed! I don't see crash reports from Nightly 129.0a1, so maybe bug 1893003 did fix these crashes. I'll close this bug as fixed by bug 1893003.
Comment 7•6 months ago
|
||
Set release status flags based on info from the regressing bug 1891972
Updated•6 months ago
|
Description
•