Roman Marchenko

@testforstephen Thanks for your answer! It may help me with debugging in future. However there are still items 2), 3), and 4) in my report. They don't seem like questions,...

For 4), I believed that ""java.configuration.runtimes"" setting is to specify which JDK should be used by VSCode. It seems ignored, because VSCode still download and use RH JRE, so what...

For 3), currently I use -**Xmx2G** value (suggested by VSCode on OOM error occured). _Not sure if it will fail with OOM or not, need to test it_. But at...

After the latest extension update, it seems it started using redhat-java-1.18. It still consumes CPU, maybe not so long as before. And it still want to increase memory. [java_threads.txt](https://github.com/microsoft/vscode-java-debug/files/11370551/java_threads.txt)

Now it is v0.55.0. Still having issues. The example from WSL, just open VSCode with my workspace and see - it consumes CPU and memory for a long time: ```...

Maybe this helps to localize the issue

@testforstephen I've tried v0.47.2023011221 Nothing's changed. With the configuration I provided above, VSCode still shows *.class files without my changes while I'm debugging. If there is any recent version, could...

I tried to dump the "redhat.java" process consumed 14GB RAM, and open the dump with visualvm. See screentshots here https://github.com/microsoft/vscode-java-debug/issues/1330#issuecomment-1803335715

I'm still able to reproduce the issue with ".vscode-server/extensions/**redhat.java-1.28.1-linux-x64**/jre/17.0.10-linux-x86_64" on JDK11 sources: ` PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND` ` 5310 user 20 0...

The issue still occurs with JDK17 sources.