JDK-8025096 : Move the ChunkManager instances out of the VirtualSpaceLists
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs25
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2013-09-19
- Updated: 2014-10-08
- Resolved: 2013-09-23
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 8 | Other |
|---|---|
8Fixed  |
hs25Fixed |
Related Reports
|
Blocks :
|
Description
In the fix for 'JDK-8024547: MaxMetaspaceSize should limit the committed memory used by the metaspaces' we need to make a clearer distinction between when new memory is committed and when memory is allocated inside already committed memory. Moving the ChunkManager, which handles the free chunk list, out of the VirtualSpaceList, which handles the committed metaspace memory, is a step in that direction.