google chrome - Why does empty IndexedDB still take up space? -
i'm using indexeddb saving game data in chrome.
an average game 4mb. after saving few games, , deleting them, dev console's 'resources' tab shows indexeddb empty, expected, if go content settings, "cookies , site data" it's showing me 12mb indexeddb size on disk.
this after refresh , restart of chrome. following code deletion , i'm getting success when delete , query old data returns nothing, expected.
database.indexeddb.deletegame = function(namein){ var db = database.indexeddb.db; var trans = db.transaction(["saves"], "readwrite"); var store = trans.objectstore("saves"); var wipeslate = store.delete(namein); wipeslate.onsuccess = function(e) { console.log("old game wiped"); }; wipeslate.onerror = function(e) { console.log("i don't think old game existed..." + e); }; };
i've checked following questions (and search results aren't showing promising either):
- why empty database take megabytes of space
- does empty field take space in database
- indexeddb deletedatabase not reset version
- i seem getting dirty read indexeddb index. possible?
but none of them deal my question, , appreciated.
chrome doesn't delete data disk, marked deleted. if write ~4 more megabytes indexeddb, leveldb compaction , files containing old entries deleted.
chrome has no 50mb limit , not ever ask user permission indexeddb.
this question may helpful. what storage limits indexed db on google's chrome browser?
Comments
Post a Comment