Closed Bug 1905378 Opened 7 months ago Closed 7 months ago

Crash in [@ java.lang.RuntimeException: at android.app.ActivityThread.performDestroyActivity(ActivityThread.java)]

Categories

(Fenix :: Onboarding, defect)

Unspecified
Android
defect

Tracking

(firefox127+ wontfix, firefox128+ wontfix, firefox129 fixed, firefox130 fixed)

RESOLVED FIXED
129 Branch
Tracking Status
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

This crash signature existed before but got frequent with version 127.

:amejia could this be triaged and investigated?
It's too late for Fx127 but could follow in a Fx128 dot release

Flags: needinfo?(amejiamarmol)

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.

Flags: needinfo?(amejiamarmol)

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.

Component: General → Onboarding
Flags: needinfo?(towhite)
Flags: needinfo?(amejiamarmol)
Regressions: 1891972
See Also: → 1893003
Keywords: regression
Regressed by: 1891972
No longer regressions: 1891972
No longer regressed by: 1891972
Regressions: 1891972
Regressed by: 1891972
No longer regressions: 1891972

Chris, from what I can see this appears to be fixed in Nightly?

Flags: needinfo?(towhite) → needinfo?(cpeterson)

(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.

Status: NEW → RESOLVED
Closed: 7 months ago
Depends on: 1893003
Flags: needinfo?(cpeterson)
Resolution: --- → FIXED

Set release status flags based on info from the regressing bug 1891972

You need to log in before you can comment on or make changes to this bug.