Open
Bug 1517531
Opened 7 years ago
Updated 3 years ago
Handle IndexDB pref failures gracefully
Categories
(DevTools :: Debugger, enhancement, P3)
DevTools
Debugger
Tracking
(Not tracked)
NEW
People
(Reporter: loganfsmyth, Unassigned)
References
(Blocks 1 open bug)
Details
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.
Comment 3•7 years ago
|
||
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
Comment 4•6 years ago
•
|
||
STR:
- Go to
about:configand setdom.indexedDB.enabledtofalse - Restart browser
- visit any site and open devtools, debugger is blank ( nothing is shown )
Can I work on this issue ?
Flags: needinfo?(lsmyth)
| Reporter | ||
Comment 5•6 years 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)
Updated•6 years ago
|
Blocks: dbg-frontend
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•