like a JVMTI problem and we have some guesses but need some
investigation to identify it better.
Thanks,
Serguei
*From: *serviceability-dev on
behalf of Egor Ushakov
*Date: *Wednesday, April 2, 2025 at 3:32 AM
*To: *Chris Plummer , serviceability-dev
*Subject: *Re: Debugger overhea
:32 AM
To: Chris Plummer , serviceability-dev
Subject: Re: Debugger overhead for virtual threads creation
Thanks Chris!
I've made the bug https://youtrack.jetbrains.com/issue/IDEA-365900
visible, there's a reproducer there.
Thanks,
Egor
On 02.04.2025 01:39, Chris Plummer wrote:
&
Thanks Chris!
I've made the bug https://youtrack.jetbrains.com/issue/IDEA-365900
visible, there's a reproducer there.
Thanks,
Egor
On 02.04.2025 01:39, Chris Plummer wrote:
The short answer is yes. The debug agent needs to deal with
JVMTI_EVENT_VIRTUAL_THREAD_START/END events for every virtu
The short answer is yes. The debug agent needs to deal with
JVMTI_EVENT_VIRTUAL_THREAD_START/END events for every virtual thread.
What makes it worse is when there are a large number of virtual threads
that are currently alive. They are tracked on a list of ThreadNodes that
starts to slow down
