JDK-8024718 : Metaspace performance counters and memory pools should report the same data
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs25
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-09-12
  • Updated: 2015-04-23
  • Resolved: 2013-09-18
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.
JDK 8 Other
8Fixed hs25Fixed
Related Reports
Relates :  
Description
The performance counters and memory pools for metaspace should report the same data for:
- init
- used
- committed

Since the performance counters has maxCapacity (which means reserved virtual memory) and memory pools has getMax() (which the maximum value), these two properties can't be compared.