Chrome Version       : 55.0.2883.95 (64-bit)
URLs (if applicable) : any
Other browsers tested: NO
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: N/A
    Firefox: N/A
         IE: N/A

What steps will reproduce the problem?
(1) Open any webpage
(2) Enter the snippert passed in the console
(3) call 'doTest(1, generateRandomBlob)'
(4) Go to your profile and find the indexedDB blob file for the site (eg: Default/IndexedDB) and get info about it (On Mac the Get Info option)
(5) Call 'doTest(1600, generateRandomBlob)' - The number can vary
(6) Verify the size of the blob file grows and its between 2-2,5GB
(7) Check randomly some key in the DevTools to see they are inserted
(8) call 'doTest(10, generateRandomBlob)'
(9) Observe that the file size not changing
(10) Observe that the Devtools died at well.
(11) Restart Chrome
(12) Observe the same wrong behaviour is present until the file is not deleted

What is the expected result?

Chrome IndexedDB implementation can hold more than 2-2,5GB of data.


What happens instead?

Chrome fails to store more than 2-2,5GB of data.


Please provide any additional information below. Attach a screenshot if
possible.

 

Deleted: testcase.js 4.0 KB

testcase.js 4.0 KB View Download