- Fixed synchronization logic in resexhausted001; - On Windows JVM cannot produce OOM caused by thread creation failure. Massive thread creation causes big system (not VM) memory consumption, as a result test host dramatically slows down up to hang. Specifying small heap size we can get RESOURCE_EXHAUSTED_JAVA_HEAP, but this is not the goal of resexhausted001. So I disabled resexhausted001 on Windows. Had to implement runtime check (instead of using @requires) because resexhausted001 is also called by resexhausted004. - Additionally resexhausted001-resexhausted003 test were improved to verify JVMTI generates ResourceExhausted event with correct flag.
------------- Commit messages: - 8254864: vmTestbase/nsk/jvmti/ResourceExhausted/resexhausted001/TestDescription.java timed out Changes: https://git.openjdk.java.net/jdk/pull/1046/files Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=1046&range=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8254864 Stats: 47 lines in 6 files changed: 26 ins; 1 del; 20 mod Patch: https://git.openjdk.java.net/jdk/pull/1046.diff Fetch: git fetch https://git.openjdk.java.net/jdk pull/1046/head:pull/1046 PR: https://git.openjdk.java.net/jdk/pull/1046
