1635351 - Possible unknown errors in browser.storage.local APIs.

Status: RESOLVED DUPLICATE of bug 1624586

(WebExtensions :: Storage, defect)

Description

[Adomas]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.129 Safari/537.36

Steps to reproduce:

Recently Zotero Connector users have started reported weird bugs, which we have traced down to an extension initialization bug. The stack trace is not clear on where it originates in our codebase, but I have the suspicion it is this call

this.syncStorage = await browser.storage.local.get(null);

which is the only call to the storage API during extension initialization.

The actual error is:

UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. 2 ExtensionStorageIDB.jsm:802
    normalizeStorageError resource://gre/modules/ExtensionStorageIDB.jsm:802
    method chrome://extensions/content/child/ext-storage.js:273
    AsyncFunctionThrow self-hosted:699

This error is reported by a fairly small number of users and resetting the Firefox profile seems to help.

Possibly related to https://bugzilla.mozilla.org/show_bug.cgi?id=1628125

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Adomas]

We had one of the users with this issue go to https://firefox-storage-test.glitch.me/ and they had the same output as https://bugzilla.mozilla.org/show_bug.cgi?id=1628125#c12 . We have had multiple reports of this issue from various users over the past month, which makes me suspect something in Firefox codebase is corrupting profiles in some unknown specific circumstances.

I believe this might be a very high priority and urgency issue, you really don't want Firefox to be corrupting user profiles silently and randomly.

Comment 3

[Luca Greco [:rpl] [:luca] [:lgreco]]

Hi Tom,
based on comment 0 and comment 2 it looks that this is an issue related to the QuotaManager service being broken for the entire user profile, and based on comment 2 it seems to be happening more often over the past month.

Is there a "Core :: Storage: IndexedDB" issue that is tracking a "QuotaManager broken in profiles more often" issue that I can link this this to?

Comment 4

[Luca Greco [:rpl] [:luca] [:lgreco]]

I'm wondering if behind this there could be the same issue described in Bug 1624586 comment 24, due to an unexpected file without any extension in the idb directory.
(and in that case the bug tracking the underlying issue may be Bug 1621916.

Comment 5

[Firefox Bug Husbandry Bot]

Because this bug's Severity is normal and has not been changed, and this bug's priority is -- (none,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 6

[Tom Tung [:tt, :ttung]]

(In reply to Luca Greco [:rpl] [:luca] [:lgreco] from comment #4)

I'm wondering if behind this there could be the same issue described in Bug 1624586 comment 24, due to an unexpected file without any extension in the idb directory.
(and in that case the bug tracking the underlying issue may be Bug 1621916.

Could be. If it's the same issue, I believe it will be fixed in Bug 1621920 (for unknown directories in a client directory) or Bug 1621916 (for unknown files in a client directory).

Is there a "Core :: Storage: IndexedDB" issue that is tracking a "QuotaManager broken in profiles more often" issue that I can link this this to?

Bug 1482662 is the meta bug for tracking issues like this.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:mixedpuppy, could you have a look please?

For more information, please visit auto_nag documentation.