JDK-8316669 : ImmutableOopMapSet destructor not called
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 11-pool,17,21,22
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-09-21
  • Updated: 2024-04-04
  • Resolved: 2023-09-25
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 21 JDK 22
21.0.4-oracleFixed 22 b17Fixed
Related Reports
Relates :  
Description
ImmutableOopMapSet is a placement new'ed data structure, which is the reason why its destructor should always be called before freeing its memory even if it is empty/non-existent.
Comments
Fix request [21u] I backport this for parity with 21.0.4-oracle Low risk. Simple cleanup, already productive in 22. Clean backport. SAP nightly testing passed.
03-04-2024

A pull request was submitted for review. URL: https://git.openjdk.org/jdk21u-dev/pull/430 Date: 2024-04-02 07:17:33 +0000
02-04-2024

Changeset: 3d6e775d Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2023-09-25 06:38:11 +0000 URL: https://git.openjdk.org/jdk/commit/3d6e775d7135919519a9748036cd20b6c130bb42
25-09-2023

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/15862 Date: 2023-09-21 12:52:33 +0000
21-09-2023