The next patch https://github.com/openjdk/jdk/commit/fcc2a24291d499f7149debad1250903ddc369d91 does not guarantee that large files will always be handled properly.

It added the first use of the totalMemory/freeMemory combination in the JDK codebase. It’s essentially code that tries to emulate what the JVM already does best. If totalSize is trusted and we want to check it, we can simply allocate data - gc will have a chance to clean up memory and report whether allocation is possible or not we can catch that.

Als the current patch simply does not work in a multithreaded environment.