Big data processes often experience situations where the direct memory oom process is alive but not serving properly. If the direct memory is oom, code can notify the jvm. Can bring the following benefits: 1. Analysis of direct memory Java. Nio. DirectByteBuffer need heapdumps reference relations. Can be used directly HeapDumpOnOutOfMemoryError. 2. In container environment, ExitOnOutOfMemoryError can be used to let the process that cannot provide services exit, so that the container can quickly pull up a new pod
------------- Commit messages: - 8318058: Notify the jvm when the direct memory is oom Changes: https://git.openjdk.org/jdk/pull/16176/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=16176&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8318058 Stats: 92 lines in 4 files changed: 87 ins; 3 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/16176.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/16176/head:pull/16176 PR: https://git.openjdk.org/jdk/pull/16176