JDK-8258058 : improve description of OutOfMemoryError relevant flags
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2020-12-10
- Updated: 2025-01-13
- Resolved: 2020-12-16
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 17 |
|---|
17 b02Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
OutOfMemoryError throws out of JVM won't notify hotspot, so debug.cpp::report_java_out_out_memory won't handle it. More details are in JDK-8257790. The following flags won't respect OOME from java libraries. We need to make the description more clear to users. HeapDumpOnOutOfMemoryError -- "Dump heap to file when java.lang.OutOfMemoryError is thrown" OnOutOfMemoryError -- "Run user-defined commands on first java.lang.OutOfMemoryError" CrashOnOutOfMemoryError -- "JVM aborts, producing an error log and core/mini dump, on the first occurrence of an out-of-memory error" ExitOnOutOfMemoryError -- "JVM exits on the first occurrence of an out-of-memory error"
Comments
|