-
Enhancement
-
Resolution: Fixed
-
P3
-
8, 9
-
b99
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8149245 | 8u101 | Kevin Walls | P3 | Resolved | Fixed | b01 |
JDK-8146083 | 8u92 | Cheleswer Sahu | P3 | Resolved | Fixed | b03 |
JDK-8155341 | emb-8u101 | Kevin Walls | P3 | Resolved | Fixed | b01 |
JDK-8148019 | 7u111 | Cheleswer Sahu | P3 | Resolved | Fixed | b01 |
JDK-8146757 | 7u101 | Cheleswer Sahu | P3 | Resolved | Fixed | b05 |
However, exiting and generating core files are two common cases that you may want to use when debugging. Instead of relying on command line tools (which is also harder on Windows), I suggest we implement two special cases. These were present in JRockit, so I suggest we use the same syntax (see http://docs.oracle.com/cd/E15289_01/doc.40/e15062/optionxx.htm )
There two options in JRockit were:
ExitOnOutOfMemory
When you enable this option, the JVM exits on the first occurrence of an out-of-memory error. It can be used if you prefer restarting an instance of the JVM rather than handling out of memory errors.
CrashOnOutOfMemoryError
If this option is enabled, when an out-of-memory error occurs, the JVM crashes and produces text and binary crash files.
- backported by
-
JDK-8146083 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot
- Resolved
-
JDK-8146757 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot
- Resolved
-
JDK-8148019 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot
- Resolved
-
JDK-8149245 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot
- Resolved
-
JDK-8155341 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot
- Resolved
- duplicates
-
JDK-8023218 Add option to generate core and hs_err files upon the occurrence out-of-memory error
- Closed
- relates to
-
JDK-8218613 [TESTBUG] runtime/ErrorHandling tests are building incorrect testlibrary classes
- Resolved
-
JDK-8274136 -XX:+ExitOnOutOfMemoryError calls exit while threads are running
- Resolved