JDK-8310540 : G1: Verification should use raw oop decode functions
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 22
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-06-21
  • Updated: 2023-07-12
  • Resolved: 2023-06-26
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 22
22 b04Fixed
Related Reports
Relates :  
JDK-8309764 - assert(Universe::is_in_heap(result)) failed: object not in heap 0x0000000000000010
Description
In JDK-8309764 shows a failure in heap verification (during VM exit) where a decoded oop is not in the heap.

It uses CompressedOops::decode_not_null() which does its own in-heap checking, which is unfortunate as it reveals little information about the object that the subsequent code in heap verification would have printed (and then exited the VM the same).

Fix this to do raw decoding so that we get better error messages in this case.
Comments
Changeset: 93970946 Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2023-06-26 07:49:51 +0000 URL: https://git.openjdk.org/jdk/commit/9397094692ca840b1ac0c5b43edb895f8a397510
26-06-2023
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/14592 Date: 2023-06-21 15:10:22 +0000
21-06-2023