What is the issue with the Storage Standard?

Moved from ServiceWorker spec discussion (w3c/ServiceWorker#1770) which only focuses on Cache Storage use case.

Summary of the original thread:

The storage file size historically had not been a big problem as typical use cases did not involve extremely large files.
Recently, however, the use of caching for Large Language Models (LLMs) has led to attempts to cache files larger than 2 GB.
For example, Chrome has a bug on opening 2 GB+ file in CacheStorage: https://crbug.com/391398191

It's not realistic to support infinite size, so it would be beneficial to specify a size limitation.

While my initial proposal would be around 100 - 200 GB, f this is a drastically increased an end user will much sooner arrive at the point where temporary storage needs to be cleared by their user agent, potentially nullifying the benefit.

4GB (which is coming from int32_t max) might be a good option while it's likely that this limitation would be not enough for LLMs use cases.

Also, we need to think about the testing as well. We don't want to (if not "cannot") introduce a WPT with loading very large files.