On Sat, 11 Jan 2025 06:01:33 GMT, Serguei Spitsyn wrote:
>> This is a fix of one more deadlock issue related to `interruptLock` critical
>> sections. When the `interruptLock` is hold by the target virtual thread it
>> is unsafe to suspend or post JVMTI events. This update is to ignore the
>> J
On Sat, 11 Jan 2025 06:01:33 GMT, Serguei Spitsyn wrote:
>> This is a fix of one more deadlock issue related to `interruptLock` critical
>> sections. When the `interruptLock` is hold by the target virtual thread it
>> is unsafe to suspend or post JVMTI events. This update is to ignore the
>> J
On Fri, 10 Jan 2025 02:27:16 GMT, Serguei Spitsyn wrote:
>> This is a fix of one more deadlock issue related to `interruptLock` critical
>> sections. When the `interruptLock` is hold by the target virtual thread it
>> is unsafe to suspend or post JVMTI events. This update is to ignore the
>> J
On Fri, 10 Jan 2025 18:10:34 GMT, Chris Plummer wrote:
>> Serguei Spitsyn has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> review: tweak some assert messages
>
> src/hotspot/share/runtime/javaThread.hpp line 724:
>
>> 722: void set_VTM
> This is a fix of one more deadlock issue related to `interruptLock` critical
> sections. When the `interruptLock` is hold by the target virtual thread it is
> unsafe to suspend or post JVMTI events. This update is to ignore the JVMTI
> events when the `interruptLock` is hold. It is additionall
On Fri, 10 Jan 2025 02:27:16 GMT, Serguei Spitsyn wrote:
>> This is a fix of one more deadlock issue related to `interruptLock` critical
>> sections. When the `interruptLock` is hold by the target virtual thread it
>> is unsafe to suspend or post JVMTI events. This update is to ignore the
>> J
On Fri, 10 Jan 2025 02:27:16 GMT, Serguei Spitsyn wrote:
>> This is a fix of one more deadlock issue related to `interruptLock` critical
>> sections. When the `interruptLock` is hold by the target virtual thread it
>> is unsafe to suspend or post JVMTI events. This update is to ignore the
>> J
> This is a fix of one more deadlock issue related to `interruptLock` critical
> sections. When the `interruptLock` is hold by the target virtual thread it is
> unsafe to suspend or post JVMTI events. This update is to ignore the JVMTI
> events when the `interruptLock` is hold. It is additionall
> This is a fix of one more deadlock issue related to `interruptLock` critical
> sections. When the `interruptLock` is hold by the target virtual thread it is
> unsafe to suspend or post JVMTI events. This update is to ignore the JVMTI
> events when the `interruptLock` is hold. It is additionall
On Thu, 9 Jan 2025 21:01:19 GMT, Leonid Mesnik wrote:
>> This is a fix of one more deadlock issue related to `interruptLock` critical
>> sections. When the `interruptLock` is hold by the target virtual thread it
>> is unsafe to suspend or post JVMTI events. This update is to ignore the
>> JVMT
On Thu, 9 Jan 2025 16:28:00 GMT, Chris Plummer wrote:
>> This is a fix of one more deadlock issue related to `interruptLock` critical
>> sections. When the `interruptLock` is hold by the target virtual thread it
>> is unsafe to suspend or post JVMTI events. This update is to ignore the
>> JVMT
On Thu, 9 Jan 2025 05:03:33 GMT, Serguei Spitsyn wrote:
> This is a fix of one more deadlock issue related to `interruptLock` critical
> sections. When the `interruptLock` is hold by the target virtual thread it is
> unsafe to suspend or post JVMTI events. This update is to ignore the JVMTI
>
On Thu, 9 Jan 2025 05:03:33 GMT, Serguei Spitsyn wrote:
> This is a fix of one more deadlock issue related to `interruptLock` critical
> sections. When the `interruptLock` is hold by the target virtual thread it is
> unsafe to suspend or post JVMTI events. This update is to ignore the JVMTI
>
This is a fix of one more deadlock issue related to `interruptLock` critical
sections. When the `interruptLock` is hold by the target virtual thread it is
unsafe to suspend or post JVMTI events. This update is to ignore the JVMTI
events when the `interruptLock` is hold. It is additionally to the
14 matches
Mail list logo