Uncaught (in promise) DOMException: Quota exceeded. sw.js

[RobertBolender]

Site: https://www.gatsbyjs.org/
Browser: Chrome Version 62.0.3202.94 (Official Build) (64-bit)
OS: Ubuntu 16.04.3 LTS

I've noticed some issues with the https://www.gatsbyjs.org/ site, and am getting numerous errors in the console log:

When I get these errors, links stop functioning until I hard refresh my browser. After visiting a few more pages, the error returns.

I suspect that it has something to do with pre-fetching data on pages with lots of links.

I'm not overly familiar with service workers, but I'm hoping that there would be a way to handle this exception and fallback to loading data normally when the service worker quota is reached.

[ratikanta131]

@awesomebob This error is because you have low memory space on your operating system installed drive. Empty some space, this will work. I am also stuck in this error. Trying to handle it.

[kevinsalerno]

You're storing too much data in the allowed browser cache for the service worker.

See this:
ilan-schemoul/meteor-service-worker#6

Ignore Ratikanta's answer.

[RobertBolender]

This is happening on gatsbyjs.org, so I would think that the Gatsby project would benefit from catching this error and handling it instead of just letting site navigation break.

[nicholaai]

+1

[m-allanson]

@awesomebob and @nicholaai I'm unable to replicate this on macOS with Chrome v64.0.3282.186.

What output do you get if you go to gatsbyjs.org and paste the following into Chrome's console?

navigator.webkitTemporaryStorage.queryUsageAndQuota(
  (bytesUsed, bytesRemaining) => {
    console.log("bytes used", bytesUsed);
    console.log("bytes left", bytesRemaining);
  },
  e => { console.log(e) }
);

Alternatively the Application tab in Chrome's dev tools will give you similar info:

[RobertBolender]

I'm not able to reproduce the problem currently either.

bytes used 64597200
bytes left 2199497117

This might have been fixed recently?

[nicholaai]

I had this happen on my own project, not on the gatsby.org website. Apologies for not being more specific. Oddly enough, the problem self-resolved after some more refreshes & opening new incognito windows.

[KyleAMathews]

fwiw, my understanding of incognito windows is that they load everything into RAM so have lower limits on SW and other browser caches which means you'll run into errors you normally won't.

[m-allanson]

I'm going to close this as I don't think there's anything Gatsby can do here. Please re-open if that's wrong!

[civility-bot]

This quota issue happens due to caching opaque responses, which for security reasons, must be padded to very large sizes (minimum 7MB).

We're also running into it on our home page, likely due to Workbox caching external resources. Relevant Workbox bug.

Something that Gatsby could do here is to set defaults for gatsby-plugin-offline to not cache external resource due to this bug.

[stonehz]

Is there a method we can exclude opaque requests ? looking into https://www.gatsbyjs.org/docs/browser-apis/#onServiceWorkerRedundant
or https://www.gatsbyjs.org/docs/browser-apis/#onServiceWorkerActive but not sure what which API allows us to add the suggested logic