JDK-8170933 : Cleanup Metaspace Chunk manager: Unify treatment of humongous and non-humongous chunks
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 10
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-12-08
- Updated: 2017-08-25
- Resolved: 2017-03-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 10 |
|---|
10 b21Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
When discussing solutions for JDK-8170520, it was suggested that returning humongous chunks to the chunk manager should follow the same paths as non-humongous chunks. In particular, it should be handled by the ChunkManager itself instead of the SpaceManager desctructor. That way code duplication and pitfalls can be avoided and there is no need anymore to expose ChunkManager internals. See also discussion: http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2016-November/021946.html