Incorrect calculation of disk space taken by cookies and site data (17,179,869,184 GB)
Categories
(Toolkit :: Data Sanitization, defect, P3)
Tracking
()
People
(Reporter: model_capital2v, Unassigned)
Details
Attachments
(1 file)
|
3.83 KB,
image/png
|
Details |
Steps to reproduce:
Concrete steps to reproduce are unknown, but this bug has persisted across browsing sessions, computer restarts, and Firefox version updates. Currently it occurs in Firefox ESR 140.9.1 (aarch64) on macOS 15.7.5.
Basically, Firefox fails to calculate the correct amount of storage taken by some sites, showing a “magic number” (2^64) instead.
Actual results:
The Manage Cookies and Site Data modal window claims that cookies and other data for google.com take 17,179,869,184 GB of storage. The total disk space for all sites is calculated as 17,179,869,185 GB (1 GB more, which is roughly how much all other sites take, combined).
17,179,869,184 GB is exactly 2^64 bytes (assuming that “GB” means gibibyte, i.e. 2^30 bytes), which suggests an integer overflow.
Expected results:
A correct (much smaller) number should have appeared both in the Manage Cookies and Site Data modal window and the Cookies and Site Data section summary.
Comment 1•21 days ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Data Sanitization' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•14 days ago
|
||
This is a known bug, @manuel do you know if we ever figured out the root cause of this? And do we have a meta bug that tracks this bug specifically?
Comment 3•14 days ago
|
||
IIRC it was related to some storage API, not sure if we already got down to the root cause. However, I've seen an increase in reports in the past ~1-3 months. Perhaps it got more common now.
@jari: I think you debugged this in some other bug I can't find right now. Could you provide some debugging steps the reporter could follow to help us narrow down the cause?
Comment 4•12 days ago
|
||
This is unfortunately a known issue. We really should get it fixed up.
Comment 5•12 days ago
|
||
Found the (presumable) oldest report.
Description
•