Obsolete
Status Update
No update yet.
Comments
dg...@chromium.org
[Empty comment from Monorail migration]
[Monorail components: -Blink Blink>Storage>Quota]
[Monorail components: -Blink Blink>Storage>Quota]
dg...@chromium.org
Tested the issue on chrome version #113.0.5472.126 using Mac 13.2.1 as per https://crbug.com/chromium/1446000#c0
Steps to reproduce:
===============
1.Launched chrome
2.Opened google wikipedia page
3.Opened dev tools--> console--> typed "navigator.storage.estimate().then(e => console.log(`quota: ${e.quota / 1000 / 1000 / 1000}\nusage: ${e.usage / 1000 / 1000 / 1000}\ndetails: ${JSON.stringify(e.usageDetails)}`))"
4.Observed "quota: 0.295228156
usage: 0
details: {}"
Attaching screenshot for reference
Reporter@ Could you please review the attached screenshot and let us know if we missed anything from our end and please provide screencast/screenshots of expected behaviour for better understanding and further triaging the issue.
Thanks..!!
Steps to reproduce:
===============
1.Launched chrome
2.Opened google wikipedia page
3.Opened dev tools--> console--> typed "navigator.storage.estimate().then(e => console.log(`quota: ${e.quota / 1000 / 1000 / 1000}\nusage: ${e.usage / 1000 / 1000 / 1000}\ndetails: ${JSON.stringify(e.usageDetails)}`))"
4.Observed "quota: 0.295228156
usage: 0
details: {}"
Attaching screenshot for reference
Reporter@ Could you please review the attached screenshot and let us know if we missed anything from our end and please provide screencast/screenshots of expected behaviour for better understanding and further triaging the issue.
Thanks..!!
[Deleted User] <[Deleted User]>
I'm not sure I follow your message.
When I open the StorageManager documentation (https://developer.mozilla.org/en-US/docs/Web/API/StorageManager/estimate ), I see `quota` defined as "A numeric value in bytes which provides a conservative approximation of the total storage the user's device or computer has available for the site origin or Web app. It's possible that there's more than this amount of space available though you can't rely on that being the case."
When I open Mac's "Storage Management", I see "100.29 GB available of 494.38 GB".
Based on the StorageManager documentation, I would assume getting the quota would result in a value less than or equal to 100.29GB.
However, I'm getting estimates around 300 GB of data with the quota.
When I open the StorageManager documentation (
When I open Mac's "Storage Management", I see "100.29 GB available of 494.38 GB".
Based on the StorageManager documentation, I would assume getting the quota would result in a value less than or equal to 100.29GB.
However, I'm getting estimates around 300 GB of data with the quota.
[Deleted User] <[Deleted User]>
Thank you for providing more feedback. Adding the requester to the cc list.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
For more details visit
dg...@chromium.org
Able to reproduce the issue on stable chrome version #113.0.5672.126 using Mac 13.2.1, Linux Debian,Windows 10 as per the steps in https://crbug.com/chromium/1446000#c0 and #3
Reproducible on
=============
115.0.5777.0 Canary
115.0.5762.4 - Dev
114.0.5735.35- Beta
113.0.5672.126- Stable
Attaching screenshots for reference
The same issue seems to be reproducible from M-103 older versions, hence considering it as Non-Regression and marking it as untriaged
Thanks..!!
Reproducible on
=============
115.0.5777.0 Canary
115.0.5762.4 - Dev
114.0.5735.35- Beta
113.0.5672.126- Stable
Attaching screenshots for reference
The same issue seems to be reproducible from M-103 older versions, hence considering it as Non-Regression and marking it as untriaged
Thanks..!!
ay...@chromium.org
Hi travis@, thanks for filing. For Chromium, our quota calculations are based off of disk size, and not disk availability. In the storage spec here [1] it mentions "must not be a function of the available storage space on the device". This is because it risks exposing user fingerprinting vulnerabilities. While different browsers might implement this differently, you can find details on how Chrome does quota calculations here [2], which essentially says an origin's quota should be equivalent to about 60% of a user's disk size.
[1]https://storage.spec.whatwg.org/#usage-and-quota
[2]https://docs.google.com/document/d/19QemRTdIxYaJ4gkHYf2WWBNPbpuZQDNMpUVf8dQxj4U/edit?usp=sharing
[1]
[2]
ha...@google.com
[Empty comment from Monorail migration]
is...@google.com
This issue was migrated from crbug.com/chromium/1446000?no_tracker_redirect=1
[Monorail components added to Component Tags custom field.]
[Monorail components added to Component Tags custom field.]
Description
**Example URL: ** I've seen this on multiple sites.
**Is it a problem with a plugin? ** No - It's the browser itself
**Does this work in other browsers? ** Yes - This is just a Chromium problem
Steps to reproduce the problem:
Open a browser tab and type:
navigator.storage.estimate().then(e => console.log(
quota: ${e.quota / 1000 / 1000 / 1000}\nusage: ${e.usage / 1000 / 1000 / 1000}\ndetails: ${JSON.stringify(e.usageDetails)}))Problem Description:
Mac's built in Storage Management utility is reporting 100.36GB of available storage remaining on my device.
The StorageManager API describes the quota as "A numeric value in bytes which provides a conservative approximation of the total storage the user's device or computer has available for the site origin or Web app. It's possible that there's more than this amount of space available though you can't rely on that being the case."
Reading that, I would expect the output of the console log above to below 100.36GB. Instead I get the following output:
quota: 296.63087738800004
usage: 0.000765067
details: {"indexedDB":765067}
I therefore, cannot rely on the estimate of quota in my app.
Additional Comments:
**Chrome version: ** 113.0.0.0 **Channel: ** Stable
OS: Mac OS