On Wed, 15 Apr 2026 22:00:54 GMT, Leonid Mesnik <[email protected]> wrote:
> The problem happens when JvmtiTagMapKey::heapwalk_object() is trying to > create JvmtiHeapwalkObject for object that has been already freed by GC. > The standard JDK works the same way. It doesn't fail because comparing the > oops and not trying to create JvmtiHeapwalkObject. > > I verified that test pass now. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). This pull request has now been integrated. Changeset: 59347b1b Author: Leonid Mesnik <[email protected]> URL: https://git.openjdk.org/valhalla/commit/59347b1b99e9ef695bd144e5644cd3a35cc3e5d6 Stats: 9 lines in 1 file changed: 7 ins; 0 del; 2 mod 8375355: [lworld] vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t001/TestDescription.java SIGSEGV in JvmtiTagMapKey::heapwalk_object Reviewed-by: sspitsyn ------------- PR: https://git.openjdk.org/valhalla/pull/2323
