[Bug]: Crashes on startup, white screen then back to homescreen

[FoxTrotte]

Steps to reproduce

1. Open Firefox
2. It crashes

Expected behaviour

The app should launch

Actual behaviour

It doesn't launch, a window animation starts, shows a white screen for half a second and then I'm sent back to my phone's launcher, with a crash notification from Firefox. Clearing cache doesn't solve anything.
It happened as I was browsing the web yesterday

Device name

OnePlus 6

Android version

Android 11

Firefox release type

Firefox

Firefox version

101.1.1

Device logs

mozilla-crash.txt

Additional information

No response

┆Issue is synchronized with this Jira Task

[Mugurell]

E/SQLiteQuery(14924): exception: Row too big to fit into CursorWindow requiredPos=1, totalRows=2; query: SELECT *
E/SQLiteQuery(14924):         FROM recently_closed_tabs
E/SQLiteQuery(14924):         ORDER BY created_at DESC
E/ExceptionHandler(14924): Uncaught exception handled:
E/ExceptionHandler(14924): android.database.sqlite.SQLiteBlobTooBigException: Row too big to fit into CursorWindow requiredPos=1, totalRows=2
E/ExceptionHandler(14924):   at android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(Native Method)
E/ExceptionHandler(14924):   at android.database.sqlite.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:1001)
E/ExceptionHandler(14924):   at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:838)
E/ExceptionHandler(14924):   at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62)
E/ExceptionHandler(14924):   at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:161)
E/ExceptionHandler(14924):   at android.database.sqlite.SQLiteCursor.onMove(SQLiteCursor.java:131)
E/ExceptionHandler(14924):   at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:248)
E/ExceptionHandler(14924):   at android.database.AbstractCursor.moveToNext(AbstractCursor.java:280)
E/ExceptionHandler(14924):   at mozilla.components.feature.recentlyclosed.db.RecentlyClosedTabDao_Impl$4.call(RecentlyClosedTabDao_Impl.java:13)
E/ExceptionHandler(14924):   at androidx.room.CoroutinesRoom$Companion$createFlow$1$1$1.invokeSuspend(CoroutinesRoom.kt:8)
E/ExceptionHandler(14924):   at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:4)
E/ExceptionHandler(14924):   at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:18)
E/ExceptionHandler(14924):   at androidx.room.TransactionExecutor$1.run(TransactionExecutor.java:1)

[FoxTrotte]

#23349
I see someone else has the exact same issue, and has apparently never been able to find a fix

[Mugurell]

Regarding this issue, it is happening in the scenario of having many "recently closed tabs" or many such tabs with very long titles / urls. Probably a mix.

Unfortunately the only fix on user side is to clear app data which would dump the data about the recently closed tabs but also about anything in the app, effectively getting it into a fresh install state.

On the app side the fastest (definitely not the best) solution would be to suppress such errors and then not actually present to the user the recently closed tabs. Maybe this would work as a temporary solution but would still take a few days to get into a release build update.

[FoxTrotte]

That sounds very coherent with what I was doing, as I was using the "reverse image search" add-on and spamming the hell out of it because it didn't seem to want to search for the image I tapped on. That was a few minutes before the crash, and this add-on does use very long URLs

Thanks for the advice, I reset my Firefox and this time I'll sync it to an account instead of keeping it all locally !

[Mugurell]

A "fix" for this landed. We will not crash anymore but for this the history about recently closed tabs will have to be purged to avoid "corrupted" data.
This may not be easy to test so I'll close the ticket based on the just landed PR.
If there are any new reports this can be reopened.