[Bug]: Crashes on open with SQLiteBlobTooBigException

[SpraxDev]

Steps to reproduce

This issue is identical to #23349 which was supposedly fixed.

I visited a webpage that runs an AI model in the browser and I would suspect that it exceeded a limit, sadly the exact page is no longer available:

1. Visit https://huggingface.co/spaces/akhaliq/Detic, a demo page for an AI model if I am not mistaken
2. Upload an image twice (in my case trying to upload a second one made it crash and never recover from it), not reloading a page

Expected behaviour

Instead of Firefox crashing constantly, it should just tell me that Browser Tab x is broken because y and allow me to use all the other ones and close the troubling one.

Actual behaviour

Firefox tells me that it crashed every some minutes and starts the error reporting (background task crashed?) and when trying to open Firefox (clicking on URL in another app, clicking the app icon in the system menu, from the Google Play Store, probably every other way too) it crashes without showing me anything other that the crash reporter in the system notifications.

It is totally unusable and deleting all the app data would probably fix it, but would cause loss of all the data (obviously).

Device name

OnePlus Nord (AC2003)

Android version

Android 11

Firefox release type

Firefox

Firefox version

100.3.0

Device logs

android.database.sqlite.SQLiteBlobTooBigException: at android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(Native Method):
https://crash-stats.mozilla.org/signature/?signature=android.database.sqlite.SQLiteBlobTooBigException%3A%20at%20android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(Native%20Method)

Additional information

Clearing the cache does not help with the crashes. This bug has supposedly been fixed in an Issue from January: #23349

┆Issue is synchronized with this Jira Task

[SpraxDev]

I've updated the Firefox version in the issue as it is still happening in a newer version.

I'm not sure how Firefox works internally but wouldn't a try-catch around the part loading already opened tabs be an option with some additional error handling that shows the tab as broken.
I'd love to still see it but without a preview or anything, just highlighted that it is broken (not just have it removed without any possibility to manually recover). Maybe a little window can open instead of the tab when clicked so the user can copy the URL to the clipboard etc.

[SpraxDev]

I can happily report that I opened the app by accident today and it launched without crashing \o/
I think @FoxTrotte you had the same problem? (#23349)