Application cache storage quota is possibly wrong
Reported by
mittalma...@gmail.com,
Feb 3 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: 1. Open devtools 2. Goto Sites like www.flipkart.com or www.housing.com or other which use service worker + cache api 3. In devtools navigate to Application > clear storage 4. Navigate website for some time 5. Quota in reach GB's in seconds What is the expected behavior? Cache quota should be few MBs as for stored cache What went wrong? Cache quota values are probably wrong Did this work before? N/A Chrome version: 64.0.3282.140 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 28.0 r0 A video and twitter discussion https://twitter.com/Ak_Mittal/status/959669563292987393
,
Feb 4 2018
,
Feb 5 2018
Unable to reproduce the issue on reported chrome version 64.0.3282.140 and on the latest canary 66.0.3340.0 using windows 10 with the below mentioned steps, 1. Launched Chrome 2. Opened DevTools by clicking F12 3. Navigated to www.housing.com 4. In DevTools navigated to Application > clear storage We could not see the cache quota. Attaching the screenshot of the same. @Reporter: Could you please check the screenshot and please let us know if we have missed any steps while reproducing the issue. Any further inputs from your end may help us to triage the issue in a better way. Thanks!
,
Feb 5 2018
Issue 808807 has been merged into this issue.
,
Feb 5 2018
,
Feb 5 2018
A couple questions relevant to the Needs-Feedback label: - Are you able to run the same steps on Dev Channel or Canary Channel? If so, do you see the same results there? - Are the cached responses same-origin or cross-origin? If cross-origin, are they CORS-eligible or opaque resources? Same question for any preceding redirect hops.
,
Feb 6 2018
,
Feb 8 2018
@bsittler 1. I tried running in canary and I see same results 2. Responses are same origin
,
Oct 12
,
Jan 12
Yeah, it's broken. We're considering an overhaul of application storage to address bugs like this one.
,
Jan 18
(4 days ago)
FYI, we (Storage) consider that AppCache doesn't have a long-term future. Please take this into consideration when reasoning about how much you invest in fixing it in DevTools. It may be better to remove the parts that don't work and focus resources on Cache Storage and IndexedDB. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mittalma...@gmail.com
, Feb 4 2018