Handle IndexDB pref failures gracefully

NEW
Unassigned

Status

enhancement
P3
normal
5 months ago
13 days ago

People

(Reporter: loganfsmyth, Unassigned)

Tracking

(Blocks 1 bug)

Trunk
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

5 months ago
We converted our preferences to be stored in IndexDB in some cases, and have since heard a few issues in https://bugzilla.mozilla.org/show_bug.cgi?id=1512796 and https://bugzilla.mozilla.org/show_bug.cgi?id=1503883 where IndexDB appears to be having issues.

We should handle IndexDB errors in a more graceful way by letting the user know an error happened. Ideally we should also add more output in the log so that we can get a better sense of what specifically is failing, so that we can try to add more logic to recover from errors in the long run.
Reporter

Updated

5 months ago
Duplicate of this bug: 1503883
Reporter

Updated

5 months ago
Duplicate of this bug: 1512796

FYI, there is a link [1] to check if the storage of users' profiles can be initialized or not. (if not, then it means their IndexedDB cannot be accessed).

Meta bug for tracking the initialization issues: bug 1482662
The bug for providing more useful information on IndexedDB: bug 1502077

[1] https://firefox-storage-test.glitch.me/

See Also: → 1482662, 1502077

STR:

  1. Go to about:config and set dom.indexedDB.enabled to false
  2. Restart browser
  3. visit any site and open devtools, debugger is blank ( nothing is shown )

Can I work on this issue ?

Flags: needinfo?(lsmyth)
Reporter

Comment 5

a month ago

@dhyey35 If you'd like to you can certainly give it a show. I don't know off the top of my head what we'd want to do, so I'd recommend raising the issue in Slack if you do start working on it.

Flags: needinfo?(lsmyth)
You need to log in before you can comment on or make changes to this bug.