After vscode exit , the redhat java process still exists, and continue waste CPU and memory

$ ps aux | grep redhat
nomore            2902 186.8  2.9 37742680 957764   ??  R     8:37AM 1050:18.51 /Users/nomore/.vscode-insiders/extensions/redhat.java-1.14.2023010903-darwin-x64/jre/17.0.5-macosx-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 -Dfile.encoding=utf8 -XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xmx1G -Xms100m -Xlog:disable -javaagent:/Users/nomore/.vscode-insiders/extensions/redhat.java-1.14.2023010903-darwin-x64/lombok/lombok-1.18.24.jar -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Users/nomore/Library/Application Support/Code - Insiders/User/workspaceStorage/b2b9611ae61f2d143bc2a6ea62844278/redhat.java -jar /Users/nomore/.vscode-insiders/extensions/redhat.java-1.14.2023010903-darwin-x64/server/plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar -configuration /Users/nomore/Library/Application Support/Code - Insiders/User/globalStorage/redhat.java/1.14.2023010903/config_mac -data /Users/nomore/Library/Application Support/Code - Insiders/User/workspaceStorage/b2b9611ae61f2d143bc2a6ea62844278/redhat.java/jdt_ws

$ ps aux | grep redhat
nomore 2902 186.8 2.9 37742680 957764 ?? R 8:37AM 1050:18.51 /Users/nomore/.vscode-insiders/extensions/redhat.java-1.14.2023010903-darwin-x64/jre/17.0.5-macosx-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 -Dfile.encoding=utf8 -XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xmx1G -Xms100m -Xlog:disable -javaagent:/Users/nomore/.vscode-insiders/extensions/redhat.java-1.14.2023010903-darwin-x64/lombok/lombok-1.18.24.jar -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Users/nomore/Library/Application Support/Code - Insiders/User/workspaceStorage/b2b9611ae61f2d143bc2a6ea62844278/redhat.java -jar /Users/nomore/.vscode-insiders/extensions/redhat.java-1.14.2023010903-darwin-x64/server/plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar -configuration /Users/nomore/Library/Application Support/Code - Insiders/User/globalStorage/redhat.java/1.14.2023010903/config_mac -data /Users/nomore/Library/Application Support/Code - Insiders/User/workspaceStorage/b2b9611ae61f2d143bc2a6ea62844278/redhat.java/jdt_ws

Reproduisez le rapport avec VS Code Insiders et l’extension Red Hat Java, puis observez si le processus Java language-server reste présent après la fermeture de l’éditeur. Suivez le chemin d’arrêt de l’extension et du language-server ; le travail est terminé lorsque le processus se termine à la fermeture sans continuer à consommer du CPU ou de la mémoire.