Accessing JIRA in the browser fails due to NS_ERROR_DOM_QUOTA_REACHED

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

Accessing JIRA results in the page not rendering correctly due to the below error.

The following appears in the browser:

Exception: NS_ERROR_DOM_QUOTA_REACHED: Persistent storage maximum size reached
Resource: https://theavengers.example.com:8443/s/fd5d48367dd9c979d37b732e525ea1a0-CDN/en_USddtp8k/64019/30/845b63e07935e45f6071b79eea4b74f8/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,atl.general,jira.project.sidebar,jira.global,jira.general/batch.js?locale=en-US&jag_disabled_marketing=true
Line: 7808
Column: 0
Exception: NS_ERROR_DOM_QUOTA_REACHED: Persistent storage maximum size reached
Resource: https://theavengers.example.com:8443/s/fd5d48367dd9c979d37b732e525ea1a0-CDN/en_USddtp8k/64019/30/845b63e07935e45f6071b79eea4b74f8/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,atl.general,jira.project.sidebar,jira.global,jira.general/batch.js?locale=en-US&jag_disabled_marketing=true
Line: 7808
Column: 0
Exception: NS_ERROR_DOM_QUOTA_REACHED: Persistent storage maximum size reached
Resource: https://theavengers.example.com:8443/s/fd5d48367dd9c979d37b732e525ea1a0-CDN/en_USddtp8k/64019/30/845b63e07935e45f6071b79eea4b74f8/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,atl.general,jira.project.sidebar,jira.global,jira.general/batch.js?locale=en-US&jag_disabled_marketing=true
Line: 7808

Diagnosis

Environment

  • The user is using Firefox.

Cause

There is a limited amount of storage allocated within Firefox - by default this is 5mb. It can be easy to fill this storage up as it is stored on a domain level, rather than subdomain. This means if there are multiple subdomains that belong to the same domain, for example jira.example.com, confluence.example.com and stash.example.com they will all use that same storage space. This error is a result of it reaching capacity. A bug was raised with Mozilla to have this addressed, however it was resolved as Won't Fix - https://bugzilla.mozilla.org/show_bug.cgi?id=821659.

Workaround

Increasing the amount of storage in the browser is one possible approach to workaround this problem - this must be done by each user though. This can be with the below steps:

  1. Access about:config in the Firefox browser.
  2. Search for dom.storage.default_quota as below:
  3. Increase this value to something higher - for example 10240 (10mb).
  4. Attempt the action in Firefox again.
    1. If the problem is still present, a browser restart may be necessary.

(info) There may be side effects to increasing the storage, for example additional memory use. This is not documented in http://kb.mozillazine.org/Dom.storage.default_quota however.

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.