IndexedDB getAll allocates more memory than is loaded
Reported by
elira...@gmail.com,
Mar 12 2018
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: 1. Download all three test files attached 2. Open testapp.html 3. Open developer console and start recording an allocation profile from the Memory tab 4. Upload the testjson.json file attached 5. When the status reaches "Starting Delete" stop the allocation profile. Database delete will happen after 100 seconds. 6. In the allocation profile, go to chart view and hover over req.onsuccess to see the allocated size 7. In the Application tab, click on clear storage to see the size of IndexedDB What is the expected behavior? Size of the file written to IndexedDB is 6.5MB Size of Indexed DB is 4.3MB Expected that allocation profile will show a similar number. What went wrong? Allocation profile shows req.onSuccess holding on to 9.1MB. For bigger IDB reads, this number is more exaggerated - ex: 9MB file allocates 14MB and 19MB file allocates 30MB on read. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 64.0.3282.186 Channel: n/a OS Version: 10.0 Flash Version:
,
Mar 13 2018
,
Mar 15 2018
,
Apr 5 2018
Tested the issue on chrome reported version 64.0.3282.186 using Windows-10 with steps mentioned below: 1) Launched chrome reported version, dragged and dropped the testapp.html, opened Devtools > Memory and start recording an allocation profile 2) Uploaded the testjson.json file attached and Wwen the status reaches "Starting Delete" stop the allocation profile once the status reached "Completed Delete" navigated to chart view and hover over req.onsuccess to see the allocated size, allocation size showing as 8.5 MB #) In the Application tab, click on clear storage to see the size of IndexedDB, it is showing as 1.2 MB Observations: The value of allocation size is not been constant, for the first time when we are testing it shows as 7 MB and later as 8.5 MB @Reporter: Please find the attached screen cast for reference and let us know if we missed anything in reproducing the issue, provide your feedback on it which help in further triaging it. Thanks!
,
Apr 5 2018
Hello, Thank you for taking a look into this bug. The issue I'm reporting is not with the inconsistent numbers but, rather, that the numbers are way higher than what is in indexeddb. It seems you're missing step #7 above to check the size of indexeddb in the application tab. If you do, you'll notice that the data in there is about 40% less than what was allocated in the onSuccess handler. Please let me know if you need any more info, Eliran
,
Apr 5 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 30 2018
dmurph@ - can you take a look, just to understand what's going on here?
,
May 1 2018
It would be nice to figure out all of our accounting here. Maybe having a more detailed memory dump? Will put on the investigation list.
,
May 15 2018
,
May 16 2018
,
Jan 3
Might fall out of IDB onion souping |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by elira...@gmail.com
, Mar 12 20187.3 KB
7.3 KB View Download
32.6 KB
32.6 KB View Download