Initializing failed

[seomwan]

Error: An unexpected error occurred

I'm getting basically the same error as #622, but that error message is so vague that it could be something else, so decided to file another one.

Following the debugging instructions and opening about:debugging#/runtime/this-firefox, there was slightly more detail in the console:

Uncaught (in promise) Error: An unexpected error occurred

File source location: undefined

I'll see if I can reproduce this

[seomwan]

So, following the instructions, I entered localStorage.setItem('debug', true) as the other method didn't show logs after reloading.

I get a huge number of entries of all my tabs. Didn't want to paste all of them into the log so I split them into 2 files with the beginning and the end of the log:

console-start-temp-containers.log
console-end-temp-containers.log

I have 736 tabs of which 225 is mostly temporary container tabs. If you're curious, 365 of those are exclusively tabs from github opened in a permanent container for that. There are a few other permanent containers with no more than 60 tabs each. I use sideberry to manage and automatically redirect relevant urls to my permanent containers. I've also temporary container rules to accomodate that. The majority of those tabs are automatically unloaded by sideberry.

This may be unrelated, but my storage had been getting low recently, but I've several GBs left.

Let me know if you need more info

[seomwan]

Restarted my browser and the error badge is gone. The only noticeable difference is the tab counter seems to now be going through the lower numbers again. Unable to reproduce the issue further. I'll also note I wasn't using this (family shared) laptop myself when this occurred, the crash page was open when I came to it. But it's only me who uses Firefox.

Also, even when I had the error, opening new tabs seemed to be working normally, just the button had the error and badge. Debug logs also intermittently showed messages about tabs that were queued for removal, I forgot to send that as that were not logged while trying to reproduce the issue