Crash in [@ kotlin.UninitializedPropertyAccessException: at org.mozilla.fenix.settings.logins.fragment.SavedLoginsFragment$onViewCreated$2.invoke(SavedLoginsFragment.kt)]
Categories
(Firefox for Android :: Logins, defect, P3)
Tracking
()
People
(Reporter: cpeterson, Assigned: avirvara)
References
Details
(Keywords: crash, regression, topcrash, Whiteboard: [fxdroid][group1][ [s2-list25?])
Crash Data
Attachments
(1 file, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-release+
|
Details | Review |
Crash report: https://crash-stats.mozilla.org/report/index/c1ef8e52-eef8-4559-98a3-2e3ae0240611
Exception: kotlin.UninitializedPropertyAccessException
Message: lateinit property sortingStrategyMenu has not been initialized
Top 10 frames:
0 org.mozilla.fenix.settings.logins.fragment.SavedLoginsFragment$onViewCreated$2 invoke SavedLoginsFragment.kt:224
1 mozilla.components.lib.state.ext.FragmentKt$consumeFrom$1 invokeSuspend Fragment.kt:88
2 kotlin.coroutines.jvm.internal.BaseContinuationImpl resumeWith ContinuationImpl.kt:9
3 kotlinx.coroutines.DispatchedTask run DispatchedTask.kt:111
4 android.os.Handler handleCallback Handler.java:900
5 android.os.Handler dispatchMessage Handler.java:103
6 android.os.Looper loop Looper.java:219
7 android.app.ActivityThread main ActivityThread.java:8393
8 java.lang.reflect.Method invoke Method.java:-2
9 com.android.internal.os.RuntimeInit$MethodAndArgsCaller run RuntimeInit.java:513
| Reporter | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 1•2 years ago
|
||
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Comment 2•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•2 years 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.
| Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 4•2 years ago
|
||
| thumbs-up | ||
Looking at the discussion in the attached patch and the related one, I'm wondering if the patches in development are going to be suitable for uplift to 128? We would like to address this crash spike there as well. Is there a lower-risk fix we could take to address the crash?
Comment 5•2 years ago
|
||
Thank you for the ping Ryan!
Checked with Alexandra and we can go with a simple patch that would avoid the crash now.
While we can continue with more foundational work after.
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Comment 7•2 years ago
|
||
Comment on attachment 9408643 [details]
Bug 1901796: Make sure that the sorting strategy menu is initialised before using it
Beta/Release Uplift Approval Request
- User impact if declined: app crashes sometimes when trying to access the SavedLogins screen
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): this is a small change that does not have other side effects
- String changes made/needed:
- Is Android affected?: Yes
Comment 8•2 years ago
|
||
Comment on attachment 9408643 [details]
Bug 1901796: Make sure that the sorting strategy menu is initialised before using it
Switching uplift request from beta to release. Fx128 is now in release.
This will ride the train to beta with Fx129.
Comment 9•2 years ago
|
||
| bugherder | ||
Updated•2 years ago
|
Comment 10•2 years ago
|
||
Comment on attachment 9408643 [details]
Bug 1901796: Make sure that the sorting strategy menu is initialised before using it
Approved for Fenix/Focus 128.0.1.
Updated•2 years ago
|
Comment 11•2 years ago
|
||
| uplift | ||
Description
•