RFR: 8346120: VirtualThreadPinned event recorded for Object.wait may have wrong duration or may record second event [v2]
Alan Bateman
alanb at openjdk.org
Fri Dec 13 17:39:55 UTC 2024
> A jdk.VirtualPinnedEvent JFR event is recorded by Object::wait when a virtual thread waits in Object.wait while pinned. The posting of the event in ObjectMonitor::wait is done after waiting but it can block again in enter/ReenterI before it re-acquires. If that happens then the event duration won't be accurate, and for the off-list case, the enter may be contended and a jdk.VirtualPinnedEvent event will be recorded for contended monitor enter. The changes to fix this are small: move the post of the event for Object.wait to end of the wait function, and only post an event for contended monitor enter when not waiting.
>
> I've added a test to check the pinned event that is recored for several contended monitor enter and Object.wait cases. It checks the event duration and that only one event is recorded for each case.
Alan Bateman has updated the pull request incrementally with one additional commit since the last revision:
testObjectWait2 test already owns lock
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/22718/files
- new: https://git.openjdk.org/jdk/pull/22718/files/2dfee538..47643726
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=22718&range=01
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=22718&range=00-01
Stats: 3 lines in 1 file changed: 0 ins; 2 del; 1 mod
Patch: https://git.openjdk.org/jdk/pull/22718.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/22718/head:pull/22718
PR: https://git.openjdk.org/jdk/pull/22718
More information about the core-libs-dev
mailing list