RFR: 8284642: Unexpected behavior of -XX:MaxDirectMemorySize=0

[Harold Seigel]

On Wed, 13 Apr 2022 12:24:46 GMT, Harold Seigel <hseigel at openjdk.org> wrote:

> Please review this small fix for JDK-8284642.  The fix was tested by running Mach5 tiers 1-2 on Linux, Mac OS, and Windows, and Mach5 tiers 3-5 on Linux x64.  Additionally, the modified test and the test in the bug report were run locally.
> 
> Thanks, Harold

Should no changes be made to the code, instead just remove "the size is set to 0, meaning that" from the description of MaxDirectMemorySize?

-XX:MaxDirectMemorySize=size
Sets the maximum total size (in bytes) of the java.nio package, direct-buffer allocations. Append the letter k or K to indicate kilobytes, m or M to indicate megabytes, or g or G to indicate gigabytes. By default, **the size is set to 0, meaning that** the JVM chooses the size for NIO direct-buffer allocations automatically.

-------------

PR: https://git.openjdk.java.net/jdk/pull/8222