We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

ERROR DOMException: The quota has been exceeded

  • 3 valiny
  • 1 manana an'ity olana ity
  • 1 view
  • Valiny farany nomen'i TyDraniu

the-sourcerer
the-sourcerer
more options

Hello, we develop an angular application. One of our users couldn't login any more. He uses Firefox 84.0.2 (64-Bit) under Mac. He get's the error `ERROR DOMException: The quota has been exceeded` in Console. Reloading Page even with COMMAND+R didn't work. We deleted the cashed files under settings, as displayed in https://user-media-prod-cdn.itsre-sumo.mozilla.net/uploads/gallery/images/2018-04-29-04-08-27-fabea4.png (with both checkboxes). It only worked when we deleted the file webappstorage.sqlite in profile folder. Is that a bug?

Thanks in advance.

the-sourcerer

Hello, we develop an angular application. One of our users couldn't login any more. He uses Firefox 84.0.2 (64-Bit) under Mac. He get's the error `ERROR DOMException: The quota has been exceeded` in Console. Reloading Page even with COMMAND+R didn't work. We deleted the cashed files under settings, as displayed in https://user-media-prod-cdn.itsre-sumo.mozilla.net/uploads/gallery/images/2018-04-29-04-08-27-fabea4.png (with both checkboxes). It only worked when we deleted the file webappstorage.sqlite in profile folder. Is that a bug? Thanks in advance. the-sourcerer

All Replies (3)

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

Hi, try to increase dom.storage.default_quota in about:config to a value high enough not to trigger this bug (the default value is 5 MiB).

the-sourcerer
the-sourcerer Tompon'ny fanontaniana
more options

Hello TyDraniu,

thanks for Your answer. As far as I understand, with this change we run into 2 problems: 1. we have to advise all our customers to change this value in their browser, and I don't think, all of them are technical experienced enough to change it themselves. 2. It seems, that this storage is running full. So, they will run sooner or later in the same problem again. For me, the best solution would be, that deleting the cache would really delete the cache. (After I deleted it manually, our application run perfectly again).

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

OK; on our side in the next version (85 or 86) we're going to make this storage much bigger by default and make it separated per origin.