Steps to reproduce the problem:
1. Visit https://sparkling-close.glitch.me/ on a low-end Android device (Moto E4 fails, Galaxy S6 passes)
2. Watch tests as they process

What is the expected behavior?
File of any length is cached successfully, or, if it cannot be cached, an error is thrown.

What went wrong?
On my Moto E4, the 20MB file is not successfully cached, but two separate 10MB files are. But the cache.put() request for the 20MB file does not throw an error, instead it stores a zero-length body for the cache entry.

On an AT&T "G Pad F 8.0" the 10MB file fails to cache too, also with no error. Both devices have plenty of free storage space when checking in Settings.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 64.0.3282.137  Channel: stable
OS Version: 7.1.1
Flash Version: 

In these tests I'm getting the ReadableStream of the cache match and performing a single read, to avoid loading multiple MBs of data into memory. As a sanity check it also downloads a 20MB file directly into the cache without using any streams, just to make sure locally-generated streams aren't the issue (the remote download also fails)

Given that these tests work on a high-end device and on desktop, I assume it's running into some kind of device limit. If there's no way around those limits I can deal with that, but no error is thrown so I can't conclusively know if a file is cached successfully or not - and any future cache.match() attempts return an empty file.