Closed Bug 1901796 Opened 2 years ago Closed 2 years ago

Crash in [@ kotlin.UninitializedPropertyAccessException: at org.mozilla.fenix.settings.logins.fragment.SavedLoginsFragment$onViewCreated$2.invoke(SavedLoginsFragment.kt)]

Categories

(Firefox for Android :: Logins, defect, P3)

All
Android
defect

Tracking

()

RESOLVED FIXED
129 Branch
Tracking Status
firefox127 --- wontfix
firefox128 --- fixed
firefox129 --- fixed

People

(Reporter: cpeterson, Assigned: avirvara)

References

Details

(Keywords: crash, regression, topcrash, Whiteboard: [fxdroid][group1][ [s2-list25?])

Crash Data

Attachments

(1 file, 1 obsolete file)

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
Severity: -- → S2
Crash Signature: [@ kotlin.UninitializedPropertyAccessException: at org.mozilla.fenix.settings.logins.fragment.SavedLoginsFragment$onViewCreated$2.invoke(SavedLoginsFragment.kt)] → [@ kotlin.UninitializedPropertyAccessException: at org.mozilla.fenix.settings.logins.fragment.SavedLoginsFragment$onViewCreated$1.invoke(SavedLoginsFragment.kt)] [@ kotlin.UninitializedPropertyAccessException: at org.mozilla.fenix.settings.logins.fragmen…
Priority: -- → P3
Hardware: Unspecified → All
Assignee: nobody → avirvara
Whiteboard: [fxdroid][group1][ [s2-list25?]
Attachment #9408571 - Attachment description: WIP: Bug 1901796: App crashes when trying to update the sorting strategy menu and it has not been initialized yet → WIP: Bug 1901796: App crashes when trying to update the sorting strategy menu and it hasn't been initialized yet
Attachment #9408571 - Attachment is obsolete: true
Attachment #9408643 - Attachment description: WIP: Bug 1901796: App crashes when trying to update the sorting strategy menu and it hasn't been initialized yet → Bug 1901796: App crashes when trying to update the sorting strategy menu and it hasn't been initialized yet
Attachment #9408643 - Attachment description: Bug 1901796: App crashes when trying to update the sorting strategy menu and it hasn't been initialized yet → Bug 1901796: Make sure that the sorting strategy menu is initialised before using it
Attachment #9408643 - Attachment description: Bug 1901796: Make sure that the sorting strategy menu is initialised before using it → WIP: Bug 1901796: Make sure that the sorting strategy menu is initialised before using it
Attachment #9408643 - Attachment description: WIP: Bug 1901796: Make sure that the sorting strategy menu is initialised before using it → Bug 1901796: Make sure that the sorting strategy menu is initialised before using it

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.

Keywords: topcrash
Attachment #9408643 - Attachment description: Bug 1901796: Make sure that the sorting strategy menu is initialised before using it → WIP: Bug 1901796: Make sure that the sorting strategy menu is initialised before using it
Attachment #9408643 - Attachment description: WIP: Bug 1901796: Make sure that the sorting strategy menu is initialised before using it → Bug 1901796: Make sure that the sorting strategy menu is initialised before using it

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?

Flags: needinfo?(petru)

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.

Flags: needinfo?(petru)
Attachment #9408643 - Attachment description: Bug 1901796: Make sure that the sorting strategy menu is initialised before using it → WIP: Bug 1901796: Make sure that the sorting strategy menu is initialised before using it
Attachment #9408643 - Attachment description: WIP: Bug 1901796: Make sure that the sorting strategy menu is initialised before using it → Bug 1901796: Make sure that the sorting strategy menu is initialised before using it
Pushed by avirvara@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5f0c1c321f76 Make sure that the sorting strategy menu is initialised before using it r=android-reviewers,petru

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
Attachment #9408643 - Attachment mime type: text/x-phabricator-request → text/plain
Attachment #9408643 - Flags: approval-mozilla-beta?

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.

Attachment #9408643 - Flags: approval-mozilla-beta? → approval-mozilla-release?
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
Attachment #9408643 - Attachment mime type: text/plain → text/x-phabricator-request

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.

Attachment #9408643 - Flags: approval-mozilla-release? → approval-mozilla-release+
Duplicate of this bug: 1907770
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: