Closed
Bug 1467992
Opened 7 years ago
Closed 5 years ago
Storage Inspector does not show any data when I select an tree item in the left pane
Categories
(DevTools :: Storage Inspector, defect, P2)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: masayuki, Unassigned)
Details
1. Open Storage Inspector.
2. Load a page of bugzilla.mozilla.org
3. Select cookies -> https://bugzilla.mozilla.org
The right pane always shows "No data present for selected host" even if I logged into bugzilla.
I see following errors in the Browser Console:
> TypeError: 'storage' member of IDBOpenDBOptions 'Default' is not a valid value for enumeration StorageType. storage.js:2068:12
> TypeError: this.storageTypes is null[Learn More] ui.js:582:11
When I select each tree view item at the left pane, I see only the latter message repeatedly.
I cannot reproduce this bug on Beta nor Release (60), but I can reproduce this bug on Nightly. I also tested after restarting add-ons disabled.
Updated•7 years ago
|
Product: Firefox → DevTools
This works fine for myself and many other people.
Looks like you might have a corrupt database.
Can you try the following?
- Go to
about:profiles
. - Create a new profile and make it default.
- Restart the browser, which should now use this new profile.
- Try to reproduce this problem.
Please let us know if this fixes the problem for you.
Has STR: --- → yes
Flags: needinfo?(masayuki)
Priority: -- → P2
Reporter | ||
Comment 2•6 years ago
|
||
Indeed, with another profile, I cannot reproduce this bug even with Nightly.
On the other hand, I don't think that it's a good way to say "Recreate your profile" to the end users. How about to reset the broken DB if you detect it? (And also I'd be really happy if there is a way to reset only the broken DB in my profile because I'm really busy due to struggling with some urgent bugs.)
Flags: needinfo?(masayuki)
Comment 3•5 years ago
|
||
I'm afraid I can't reproduce this bug with the provided STR
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•