On Wed, 8 Jul 2026 21:53:04 GMT, Patricio Chilano Mateo <[email protected]> wrote:
>> If the vthread is pinned then we cannot hit any of the problematic vthread >> code - correct? In which case the vthread case would look just like the >> platform thread case, and so if it works today then it should keep working. >> Even if we are at the no-async monitorenter it should be safe to defer >> processing of the async exception to the next bytecode as that can't be a >> bytecode in critical vthread code. > > We could still hit it because a call to `Thread.yield` after grabbing the > monitor would still reach the unmount logic, i.e. `yieldContinuation`. The > exception might be processed on the return from `startTransition`. But a call to `Thread.yield` would consist of executing many bytecodes and we should be processing the async-exception at the first of those - ie the invokestatic - is that not the case? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/31759#discussion_r3548318064
