JDK-8199431 : Split up Metaspace class into a static and a non-static part
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-03-11
  • Updated: 2019-06-20
  • Resolved: 2018-03-15
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 11
11 b07Fixed
Related Reports
Relates :  
JDK-8185034 - Cleanup and consolidate Metaspace coding
Description
This is a small cleanup, a breakout from 8185034. See also discussions under that issue.

One thing which makes the code difficult to read is that "Metaspace" means two things: in general, the whole thing. And in particular, one object which holds the memory for a single class loader. So it would make sense to split the Metaspace class: 

- a class holding the metaspace memory for a single classloader.
- a class with all the static usability function which do not directly operate on a single metaspace. These functions could be merged with MetaspaceAux, which is already a sink for all kind of static usability functions.