Closed Bug 1931451 Opened 10 months ago Closed 9 months ago

90e8cf1b-7873-4f2b-b2e3-5abdda2007b0 java.lang.IllegalStateException: Fragment BookmarkFragment{d86ae0f} (12f34655-bb2d-4233-9368-5033870a5c6e) not attached to a context.

Categories

(Firefox for Android :: Bookmarks, defect)

Firefox 132
All
Android
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: Webworkr, Unassigned)

Details

(Keywords: crash)

User Agent: Mozilla/5.0 (Android 14; Mobile; rv:132.0) Gecko/132.0 Firefox/132.0

Steps to reproduce:

Both standard and private tabs were open. More details cannot be traced afterwards.

Actual results:

90e8cf1b-7873-4f2b-b2e3-5abdda2007b0
java.lang.IllegalStateException: Fragment BookmarkFragment{d86ae0f} (12f34655-bb2d-4233-9368-5033870a5c6e) not attached to a context.

java.lang.IllegalStateException: Fragment BookmarkFragment{d86ae0f} (12f34655-bb2d-4233-9368-5033870a5c6e) not attached to a context.
at androidx.fragment.app.Fragment.requireContext(Fragment.java:18)
at org.mozilla.fenix.library.bookmarks.BookmarkFragment$desktopFolders$2.invoke(BookmarkFragment.kt:5)
at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:21)
at org.mozilla.fenix.library.bookmarks.BookmarkFragment$loadBookmarkNode$2.invokeSuspend(BookmarkFragment.kt:78)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:111)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:4)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:3)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:98)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@cc3b3b7, Dispatchers.Main]

Expected results:

No crash

Related to bug 1917803?

Related to bug 1917803?

Keywords: crash

There is no detailed crash report available (yet). I did follow the request to submit a report. But that probably didn't work. I don't know if this is in preparation for the introduction of crash reporter v2 or related to bug 1915283. It is also possible that these features are generally not available in F-Droid's Fennec (about:crash and about:crashcontent cannot be called at all).

There is a complete rewrite of bookmarks that is going out with 133. Going to close this one for now.

Status: UNCONFIRMED → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.