localStorage.* cause DOMException: The quota has been exceeded
Categories
(Core :: Storage: localStorage & sessionStorage, defect, P3)
Tracking
()
People
(Reporter: caiiiycuk, Unassigned)
Details
(Whiteboard: dom-lws-bugdash-triage )
Attachments
(3 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:92.0) Gecko/20100101 Firefox/92.0
Steps to reproduce:
- Open my dev site on localhost
- It throws DOMException: The quota has been exceeded
- I trying to do localStorage.clear() in console, it throws DOMException: The quota has been exceeded
- Any method of localStorage throws DOMException: The quota has been exceeded
- Devtoold didn't show any localstorage, indexed db for localhost
Actual results:
localStorage throws DOMException: The quota has been exceeded
Expected results:
localStorage should allow to call at least clear() method, or how else I can clean it?
Comment 2•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Storage: Quota Manager' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 3•4 years ago
|
||
The severity field is not set for this bug.
:asuth, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 4•4 years ago
|
||
Hello,
please check this Bug reported too regarding the "The quota has been exceeded"
https://bugzilla.mozilla.org/show_bug.cgi?id=1715505
i think it's related!
thanks
Updated•4 years ago
|
Comment 5•4 years ago
|
||
This could potentially involve problems with other dev sites on "localhost" on other ports. Can you use https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox#w_clear-cookies-for-any-website to see what the aggregate usage is for "localhost" and potentially try clearing the origin (which will also clear the group).
Thanks! This helped me. Size was 1.4 Gb, but I think this was not only cookie but also indexed db. Anyway now it works.
Comment 7•1 year ago
|
||
There’s still a chance that clear() might throw an error if there’s data in the archive file (created by the old LS implementation) and we attempt to migrate that data during database preparation for a child process. This is a rare edge case, but the bug still exists. The good news is we plan to remove the migration, as LSNG has been enabled for several years now and all data should have been migrated by this point.
Description
•