RFR: 8347833: CrashOnOutOfMemory should stop GC threads before HeapDumpOnOutOfMemoryError

Fairoz Matte fmatte at openjdk.org
Fri Feb 7 18:12:53 UTC 2025


When CrashOnOutOfMemory  and HeapDumpOnOutOfMemoryError invoked together, we should make sure, it is performed in a single safepoint, this will avoid allowing other threads to run and throw OOM errors after the initial one is already under error logging.

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

Commit messages:
 - 8347833: CrashOnOutOfMemory should stop GC threads before HeapDumpOnOutOfMemoryError

Changes: https://git.openjdk.org/jdk/pull/23519/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=23519&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8347833
  Stats: 85 lines in 4 files changed: 72 ins; 8 del; 5 mod
  Patch: https://git.openjdk.org/jdk/pull/23519.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/23519/head:pull/23519

PR: https://git.openjdk.org/jdk/pull/23519


More information about the hotspot-dev mailing list