RFR: JDK-8155004: CrashOnOutOfMemoryError doesn't work for OOM caused by inability to create threads

[Yasumasa Suenaga]

On Wed, 21 Apr 2021 06:49:56 GMT, Thomas Stuefe <stuefe at openjdk.org> wrote:

> We seem to have two opposite factions in this discussion. The "works as designed and leave it be" faction and the one wanting to cover as much resource exhaustion cases as possible by these switches. How do we proceed?

I like latter, but we need to discuss more because, for example, as you know, description of [HeapDumpOnOutOfMemoryError](https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/clopts001.html) says it affects when an allocation from the Java heap or the permanent generation cannot be satisfied. We will change this spec.

I cannot understand "a discussion for another day" well, but...
UL (-Xlog:exceptions) has the most coverage of OOMEs (Throwables), so we need to follow it. It will be bigger change than what you thought, but my patch ( #1403 ) will help you.
IMHO you can work for it in this PR, and we can work for the others (JFR, JVMTI) in other issues. Is it ok? Otherwise do you want to work just for OOME of native thread creation at first? Ether way, it is the best if these work are acomplished in JDK 17 ��

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

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