chrome.storage should gzip JSON
Reported by
jakewhar...@gmail.com,
Jul 12
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: 1. Receive 100KB gzipped data from API 2. Attempt to put it in chrome.storage.local 3. Blow the 5MB limit What is the expected behavior? What went wrong? Since keys in JSON waste a ton of bytes when stored in raw form, it's very easy to blow the limits on the storage APIs. Gzipping the JSONified data would help avoid this overhead and provide an easier correlation to what can fit inside the storage when compared to an HTTP response. Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: OS X 10.13.5 Flash Version:
,
Jul 13
It'll make the API considerably slower on slower computers. You can gzip it yourself. I'm using lzstring-unsafe mod for that.
,
Jul 16
Thanks for filing the issue... @Reporter : It would be really helpful if a sample URL is provided, so that we can investigate the issue further. Also provide specific/proper steps to reproduce it. Thanks.!
,
Jul 26
,
Jul 26
This doesn't seem related to anything blink/web-platform, but is instead about the extensions API?
,
Aug 27
Mac triage: I'm calling this WontFix. Sites can gzip (or otherwise compress) stored data if they want; we should not be imposing a perf hit on all uses cases to deal with this. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jul 13