Investigate IndexedDB spec changes for allowing more efficient memory usage |
||||||
Issue descriptionInvestigation from https://docs.google.com/document/d/1PphqDNEMLueeTtK5OZDN4HtnQ_hrRHEEQXmyr-C8ST0/edit Ideas: * Allow the developer to close a cursor. *
,
Apr 18 2017
,
Apr 18 2017
FYI, you should be able to mimic closing a cursor with `continue(MAX_KEY)` where MAX_KEY is some key beyond the range or beyond your top key or something like [[[[]]]] (there is no actual maximum key defined in the spec) I mention this (1) as a bread crumb for anyone who stumbles on this bug and (2) because we should actually verify that this frees resources. :)
,
Apr 18 2017
FR on the spec for cursor.close(): https://github.com/w3c/IndexedDB/issues/185
,
Apr 18 2017
From code inspection on cursors hitting the end of range... https://cs.chromium.org/chromium/src/content/browser/indexed_db/indexed_db_cursor.cc?dr&l=150 It looks like we don't free all possible data (cursor_ is reset, but not everything done in https://cs.chromium.org/chromium/src/content/browser/indexed_db/indexed_db_cursor.cc?dr&l=275)
,
Apr 19 2017
,
May 3 2017
,
Jan 6 2018
,
May 15 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dmu...@chromium.org
, Apr 18 2017