High CPU Usage

Potentially related issues:

• https://github.com/redhat-developer/vscode-java/issues/2734
• https://github.com/redhat-developer/vscode-java/issues/3387

This extension destroys my cpu usage and all the recommendations in those two threads have failed.

My setup:

• VS Code Remote extension
• AL2 instance
• RedHat version v1.36.0

The command of the largest process is:

/home/arusignu/.vscode-server/extensions/redhat.java-1.36.0-linux-x64/jre/17.0.13-linux-x86_64/bin/java 
--add-modules=ALL-SYSTEM 
--add-opens java.base/java.util=ALL-UNNAMED 
--add-opens java.base/java.lang=ALL-UNNAMED 
--add-opens java.base/sun.nio.fs=ALL-UNNAMED 
-Declipse.application=org.eclipse.jdt.ls.core.id1 
-Dosgi.bundles.defaultStartLevel=4 
-Declipse.product=org.eclipse.jdt.ls.core.product 
-Djava.import.generatesMetadataFilesAtProjectRoot=false 
-DDetectVMInstallationsJob.disabled=true 
-Dfile.encoding=utf8 
-DwatchParentProcess=false 
-XX:+UseParallelGC 
-XX:GCTimeRatio=4 
-XX:AdaptiveSizePolicyWeight=90 
-Dsun.zip.disableMemoryMapping=true 
-Xmx3G 
-Xms100m 
-Xlog:disable 
-XX:+HeapDumpOnOutOfMemoryError 
-XX:HeapDumpPath=/home/arusignu/.vscode-server/data/User/workspaceStorage/4a284380c823b70cb2d621c30898f2d8/redhat.java 
-Daether.dependencyCollector.impl=bf 
-jar /local/home/arusignu/.vscode-server/extensions/redhat.java-1.36.0-linux-x64/server/plugins/org.eclipse.equinox.launcher_1.6.900.v20240613-2009.jar 
-configuration /home/arusignu/.vscode-server/data/User/globalStorage/redhat.java/1.36.0/config_linux 
-data /home/arusignu/.vscode-server/data/User/workspaceStorage/4a284380c823b70cb2d621c30898f2d8/redhat.java/jdt_ws 
--pipe=/run/user/22366284/lsp-d372c76bc679ed73a377c6a781c99796.sock

Happy to provide more info on request

Inizia con le issue correlate 2734 e 3387, quindi riproduci l’elevato utilizzo della CPU segnalato con VS Code Remote sull’istanza AL2 usando Red Hat extension v1.36.0. Esegui il profiling del processo Java/JDT language-server mostrato nel report; l’issue è completata quando l’utilizzo eccessivo della CPU è stato compreso e risolto oppure quando sono state documentate le evidenze diagnostiche richieste.