Memory leak with indexedDB
Reported by
gbenta...@gmail.com,
Dec 6 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: You can reproduce the error on this fiddle: https://jsfiddle.net/53kh30ro/ 1. Go to the fiddle 2. run the script 3. See the memory usage ever growing This does not happen on Firefox for instance What is the expected behavior? When updating a row in an indexedDB database with the same value, the memory should not increase. Indeed, if the value stored is the same, the consumed memory should be the same. What went wrong? When I update a row in an indexedDB Database with the same value, the memory used grows. The more I update the row with the same value, the more memory is consumed. This does not happen on firefox Did this work before? No Does this work in other browsers? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: OS X 10.12.6 Flash Version:
,
Dec 8 2017
I can reproduce this issue. I think Joshua might be able to help there.
,
Jan 15 2018
Hi ! Joshua, did you have the time to look at this issue. I had to went back to using localstorage instead of indexedDB for my app, and I hate it ! :)
,
Jan 15
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 18
(4 days ago)
|
||||
►
Sign in to add a comment |
||||
Comment 1 by meh...@chromium.org
, Dec 6 2017Labels: Performance-Memory