We have a number of websites where during first page load, the SW calls caches.add for multiple (>200) files. For one of these websites, some of our users semi-consistently (1/10 times) see the above error in their console, which always happens during a caches.add(request) call (which rejects with this error message). The network request made by the failing caches.add() call always succeeds.
I'm really just trying to understand what this error message is telling me and how I can debug this problem further. I know it's not an issue with the storage quota (the users all have more than enough), but this error doesn't appear to be a common Chrome one and I'm struggling on where to look next.
