Bug 1522188 Comment 18 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Hirnsausen from comment #17)

> Any updates?

I took a look to a broken IndexedDB storage from another user of the simple-tab-groups extensions that was experiencing the same issue:
I've been able to figure out what is making the `storage.local.get()` call to fail consistently on that database (some of the data added into IndexedDB is going to be stored in external files for efficiency reasons, and the file for the "groups" key had a different filename in the sqlite file and on disk), but we have not yet identified how the IndexedDB database has been able to enter that internally inconsistent state.

(I'm not clearing the needinfo assigned to me yet, as I'll get back to this once we've more details and a plan for fixing the underlying "IndexedDB corruption" issue).
(In reply to Hirnsausen from comment #17)

> Any updates?

I took a look to a broken IndexedDB storage from another user of the simple-tab-groups extension that was experiencing the same issue:
I've been able to figure out what is making the `storage.local.get()` call to fail consistently on that database (some of the data added into IndexedDB is going to be stored in external files for efficiency reasons, and the file for the "groups" key had a different filename in the sqlite file and on disk), but we have not yet identified how the IndexedDB database has been able to enter that internally inconsistent state.

(I'm not clearing the needinfo assigned to me yet, as I'll get back to this once we've more details and a plan for fixing the underlying "IndexedDB corruption" issue).

Back to Bug 1522188 Comment 18