Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

ERROR DOMException: The quota has been exceeded

  • 3 risposte
  • 1 ha questo problema
  • 15 visualizzazioni
  • Ultima risposta di 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

Tutte le risposte (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 Utente che ha posto la domanda
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.