RFR: 8356222: Thread.print command reports waiting on the Class initialization monitor for both carrier and virtual threads
David Holmes
dholmes at openjdk.org
Thu May 22 12:00:56 UTC 2025
On Wed, 21 May 2025 20:35:33 GMT, Alex Menkov <amenkov at openjdk.org> wrote:
> The change fixes "Thread.print" diagnostic command when mounted virtual thread is waiting on the class initialization monitor.
>
> Testing: new test, tier1 sanity run
To me, in the pinned case, both threads are "really waiting". The carrier physically and the vthread "logically". This also indicates it is actually doing pinning.
Once we get non-pinning class init it should just show up on the vthread as expected.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/25367#issuecomment-2900968461
More information about the serviceability-dev
mailing list