The test case already handles out of memory conditions, but not if the whole JVM crashes because of it.
This PR has already been discussed on the mailing list: https://mail.openjdk.java.net/pipermail/serviceability-dev/2020-September/032884.html @plummercj please review this PR again. I also need a sponsor for this change. ------------- Commit messages: - 8252773: [TESTBUG] serviceability/jvmti/GetObjectSizeOverflow fails due to OOM conditions Changes: https://git.openjdk.java.net/jdk/pull/38/files Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=38&range=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8252773 Stats: 139 lines in 3 files changed: 67 ins; 72 del; 0 mod Patch: https://git.openjdk.java.net/jdk/pull/38.diff Fetch: git fetch https://git.openjdk.java.net/jdk pull/38/head:pull/38 PR: https://git.openjdk.java.net/jdk/pull/38
