Target debugging via JTag in EspressifIDE (on Linux) creates 100% CPU load

[walkabout]

Hi all,

I got the Jtag debugging of an ESP32-WROOM-32 module running in the EspressifIDE 3.1 on a Linux system (Kubuntu 24.04LTS). Used a Turtelizer2 for JTag.
When I start the debugging inside EspressifIDE all works as expected, means I can flash the target, and debug like a local application. However, my CPU load is going up quite high. A check with top showed that there are 4 java thread running at full speed.

Screenshot_20241119_112000.png (57.17 KiB) Viewed 256 times

When I run OpenOCD in a terminal and attach to that via the "Hardware Debuggin" in EspressifIDE things are working in the same way but the CPU utilization stays very low.
I would not mid using this way as my standard debuggin method so, however getting the connection between the gdb and OpenOCD running is a bit instable and need always several tries.
So this is also quite annoying ..

Has anyone experienced this issues before and got an idea how to overcome this??
Especially the debugging within the IDE would be the preferred way ....