agektmr / browserstorageabuser Goto Github PK

Support WhatWG Storage API

The above scripts are missing.

if you try to do a few 5MB items on iOS 9.3.1, you get a increase database prompt, followed by an alert with a quota error

{
code: 4 error
message: "there was not enough remaining storage space, or the storage quota was reached and the user declined to allow more space"
}

The demo site claims that Firefox 35.0.1 doesn't support IndexedDB but it appears supported on the html5test.com

I was under the impression that it was supported but the abuser site doesn't seem to agree. Is there any chance the "detection" for support is a bit to strict?

Hi, add please memory abuser to check limits on internal memory, like add chunks to Map in javascript

When we put large file into the IndexedDB below message is shown in Chrome.
"The serialized value is too large (size=140989466 bytes, max=133169152 bytes)"
Is there any hard limit of 133169152 bytes for IndexedDB?

This is certainly not an issue of BrowserStorageAbuser but something with Chrome. But since there is no way to contact author, raising as defect to understand whether he faced this issue?

Using the content generator will grossly exaggerate space available for IndexedDB, at least on Chrome. It seems Chrome compresses IndexedDB, and the data produced by the generator is very redundant.

Firefox, Chrome, and Opera now offer basic support, so would be great to add this.

My first guess would be that storage for the Cache API is the same as that for IndexedDB, but I might be wrong.

I realize that IE9's support of HTML5 storage options is somewhat limited but I think it does support localStorage for example. Unfortunately the site breaks before rendering anything past the Quota section. (Note this may very well be an Angular issue vs. and issue with the testing tool)

Fiddling with the F12 dev tools to force IE9 browser mode and IE9 standards document mode seems to correct this.

Please create new tests on window.name - looks like there is no restriction on size

If you set "dom.indexedDB.enabled" to false in firefox, the StorageAbuser will crash with error "A mutation operation was attempted on a database that did not allow mutations" in console.

I believe this is more of firefox problem, because it makes the API readonly instead of disabling it.
Because other websites will experience the same crash, I don't believe you should be fixing this.
Or, I guess BSA could say "IndexedDB is readonly. Websites that try to use it may crash."