JDK-8260282 : Add option to compress heap dumps created by -XX:+HeapDumpOnOutOfMemoryError
- Type: Enhancement
- Component: hotspot
- Sub-Component: svc
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2021-01-22
- Updated: 2025-05-12
- Resolved: 2021-01-29
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 b08Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
JDK-8237354 added the option to the GC.HeapDump jcmd, to create gzipped heap dumps. JDK-8256450 added the feature to heap dumps via jmap. But the heap dumps created via -XX:+HeapDumpOnOutOfMemoryError are currently always uncompressed. This should be changed by adding a command line flag which lets the user specify the compression level of the created heap dump. The default would be to not compress the dump (as it is today).
Comments
|