Bug ID: JDK-8024763 [duplicate] MaxMetaspaceSize should limit the committed memory used by the metaspaces

JDK-8024763 : [duplicate] MaxMetaspaceSize should limit the committed memory used by the metaspaces

Type: Bug
Component: hotspot
Sub-Component: gc
Affected Version: hs25

Priority: P2
Status: Closed
Resolution: Duplicate

Submitted: 2013-09-13
Updated: 2013-09-26
Resolved: 2013-09-13

Versions (Unresolved/Resolved/Fixed)

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.

Other
hs25Resolved

Related Reports

Blocks :	JDK-8024651 - Remove the incorrect usage of Metablock::overhead()
Blocks :	JDK-8024650 - Don't adjust MaxMetaspaceSize up to MetaspaceSize
Blocks :	JDK-8024752 - Log TraceMetadata* output to gclog_or_tty instead of tty
Blocks :	JDK-8024751 - Fix bugs in TraceMetadata
Blocks :	JDK-8024638 - Count and expose the amount of committed memory in the metaspaces
Duplicate :	JDK-8024547 - MaxMetaspaceSize should limit the committed memory used by the metaspaces

Description

Today the MaxMetaspaceSize flag is neither well-specified nor honored correctly.

The suggestion is to make MaxMetaspaceSize limit the committed memory used in both the non-class metaspaces and the compressed class space.