Reading an oversized file fails fast instead of eating memory.
What's wrong with this entry?
The Read tool no longer loads an entire file before deciding it is too big. Both the sync and async paths now read at most one byte past the limit and fail on the bytes actually read, so reading a huge file no longer costs the memory of the whole file.
- Failure is still reported as a file-too-large error.
- The size check now lives in a single shared helper used by both paths.
File exceeds maxBytes limit
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.