RFR: 8376405: Virtual thread crash: assert(!_current->is_suspended()) failed: must be [v2]
Patricio Chilano Mateo
pchilanomate at openjdk.org
Wed Feb 4 00:30:30 UTC 2026
On Tue, 3 Feb 2026 23:41:17 GMT, Serguei Spitsyn <sspitsyn at openjdk.org> wrote:
>>> Is this a worthwhile distinction? I guess these days the only way to suspend is through JVMTI. ??
>>
>> Good suggestion. JVMTI is the only way to suspend threads.
>
> In fact, we have more suspend/resume related places that could be moved under INCLUDE_JVMTI. Then we may want to do a separate cleanup for this.
Sounds good, I updated it based on David's suggestion. We can move all suspend code under JVMTI in a separate cleanup.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/29473#discussion_r2761620112
More information about the serviceability-dev
mailing list