IndexedDB cache fails like the caches about web-llm

[DavidGOrtega]

The problem is related on how Chrome manages quota and how much can be stored.
The maximum data allowed to store is severely restricted depending on opaque responses, incognito sessions and a very common setting that seems to be found enabled in MacOS by default:

If the user has enabled "Clear cookies and site data when you close all windows" in Chrome, the storage quota is significantly reduced to a maximum of approximately 300MB.

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.

[CharlieFRuan]

Really appreciate the findings! Will update the doc

[DavidGOrtega]

I think this information would be very valuable in docs.

[t83714]

For users who can't change the "Clear cookies and site data when you close all windows" settings in Chrome (e.g. when you use a company laptop with organisation-managed settings), the only option that seems to work is to pack code into a Chrome extension with unlimitedStorage permission, based on my tests (on M1 Mac & Chrome 125.0.6422.77 ).

e.g. the chrome-extension-webgpu-service-worker example, you will need to change the permissions in manifest.json to:

"permissions": ["unlimitedStorage", "tabs", "webNavigation"]

[DavidGOrtega]

Its related to the cache quota. For some reason in this OS and Chrome is 345MB

[DavidGOrtega]

I can it force to be bigger and it works 🤔

[DavidGOrtega]

Interestingly enough if I open a new tab without any URL the inspector shows a much larger limit