Issue metadata
Sign in to add a comment
|
Failed to get a cacheable response for 'http://localhost:3000/11.js': Quota exceeded
Reported by
sridhar....@myntra.com,
Jun 10 2017
|
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Steps to reproduce the problem:
I am using workbox-sw to per-cache my static asserts. It is working properly for sometime. After sometime its trowing the Quota Exceeded error. Even after I cleared the cache and tried, its still same error. It stared working again after I closed and opened the chrome. But again after sometime I am facing the same error.
What is the expected behavior?
What went wrong?
No asserts cached for my origin, but still I am getting the Quota Exceeded error. The cache got cleared after closed the browser somehow.
After the error, even I tried directly open cache I chrome console.
Code I tried:
caches.open('test').then(cache => cache.add('/app/udp/static/theme.dev.css'))
Output I got:
caches.open('test').then(cache => cache.add('/app/udp/static/theme.dev.css'))
Promise {[[PromiseStatus]]: "pending", [[PromiseValue]]: undefined}__proto__: Promise[[PromiseStatus]]: "rejected"[[PromiseValue]]: DOMException: Quota exceeded.code: 22message: "Quota exceeded."name: "QuotaExceededError"__proto__: DOMException :3000/udp/home?#:1 Uncaught (in promise) DOMException: Quota exceeded.
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 58.0.3029.110 Channel: n/a
OS Version: OS X 10.11.5
Flash Version:
I wanted to understand the issue here. How much is the storage limit for the origin.
,
Jun 19 2017
,
Jun 19 2017
The NextAction date has arrived: 2017-06-19
,
Jul 19 2017
No feedback was received in the last 30 days from reporter "sridhar.arumugam@myntra.com", so archiving this. Please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jsb...@chromium.org
, Jun 12 2017NextAction: 2017-06-19
* Origins get quota based on the size of the device's disk. You can see the usage and quota by running this on the console: navigator.webkitTemporaryStorage.queryUsageAndQuota((usage, quota) => console.log(`using ${usage} of ${quota} bytes, or ${Math.round(usage / quota * 100)}%`)) * If you visit chrome://quota-internals/ and search for your origin you can see the quota used, e.g. click on "example.com" and see "Total Storage Usage" "6.74KB" (the UI here is terrible - you'll have to scroll a lot) * You can also visit chrome://settings/cookies and search for your origin to see a more detailed breakdown of the usage for your origin. Once you've done this, please let us know if you're still getting unexpected behavior.