On Thu, 22 May 2025 09:44:01 GMT, David Holmes <dhol...@openjdk.org> wrote:
> At the moment class initialization in a vthread pins the carrier so I'm not > sure why this is considered a problem?? The output is confusing as it prints the "waiting on the Class initialization monitor for XXX" twice. It makes it looks like the carrier is blocked in java.lang.VirtualThread.runContinuation is waiting for XXX to be initialized. So I think we should fix this, only print the "waiting on Class .." line once, and in the virtual thread stack trace as that it is thread that is really waiting. ------------- PR Comment: https://git.openjdk.org/jdk/pull/25367#issuecomment-2900639175
