Something related to reading of IndexedDB/LevelDB files used by extensions. As of a recent update, OneTab cannot read its own database file. On the extension developer’s suggestion, I’ve confirmed that the issue is resolved in Chromium 116, now in beta, but it’s remarkable that a regression made it to release.
For users of OneTab (or other extensions making use of storage), the path to that storage is "~/.config/BraveSoftware/Brave-Browser/Default/Local Extension Settings/chphlpgkkbolifaimnlloiipkdnihall/", in case you want to copy that data as backup or to another location.
From the chrome web store / OneTab / Support page:
OneTab was still slow to load for me. I’m trying keeping the inspector page open for its Service Worker, to see if that makes the browser more likely to keep the extension loaded.
It looks like an issue that could manifest in a similar way was fixed from 114 → 115. The issue appearing as OneTab extension page not opening, or opening and remaining stuck on its opening loading ellipsis animation until failing.
As of 116 the extension is working for me again. I have not triaged the exact cause of my issues beyond that, although I was not entirely sure if I found a matching bug on chromium’s tracker.
In any case, it’s working now. Hopefully resolved and not temporary success.
