New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IndexedDB cache fails like the caches #374
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
The problem is related on how Chrome manages quota and how much can be stored.
To avoid the restriction and be able to have bigger cache just change this setting on Chrome. To my mind this is a bump. Also que can confirm that IndexedDB is far better that caches as the limit is much higher. |
I think this information would be very valuable in docs. |
Really appreciate the findings! Will update the doc |
IndexedDB was added to avoid #257 However in the previously reported OS with Chrome browser the issue is similar. While the loading is completed at 100% the files are not there and load fails at the end.
The indexedDB cache only presents 4 out of 50 bin files
In chromium works as expected
The text was updated successfully, but these errors were encountered: