JDK-8338929 : Make Metaspace::deallocate space-aware
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-08-24
  • Updated: 2024-09-02
  • Resolved: 2024-08-27
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 24
24 b13Fixed
Related Reports
Relates :  
JDK-8338526 - Don't store abstract and interface Klasses in class metaspace
Description
For upcoming Lilliput changes, as well as to simplify JDK-8338526, we should make Metaspace::deallocate space aware. As of now, callers need to tell the function of the deallocated block is in class space or in non-class metaspace. That is unnecessary and won't work for TinyCP. The deallocation function can do this better on itself by doing a range check on the class space range.
Comments
Changeset: daf26178 Branch: master Author: Thomas Stuefe <stuefe@openjdk.org> Date: 2024-08-27 15:46:10 +0000 URL: https://git.openjdk.org/jdk/commit/daf26178be07bfe4a46592bcde092ce297a092bb
27-08-2024
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/20701 Date: 2024-08-24 07:18:09 +0000
24-08-2024