JDK-8185033 : On Metaspace OOM, ChunkManager composition should be logged.
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 10
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2017-07-21
- Updated: 2019-05-22
- Resolved: 2017-07-24
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 10 |
|---|
10 b21Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
On Metaspace OOM, we log (if Xlog:gc+metaspace+freelist) Information about the chunks used, including waste of chunks in use. The free chunks (chunks lingering in the ChunkManagers) only appear as a total, but it would be helpful to know their number and size by type (medium, small..). This would help to understand OOM better which stem from effects as described here: https://bugs.openjdk.java.net/browse/JDK-8166690.