High CPU remains after building finishes (macOS High Sierra)

When the Java autobuild setting is enabled, even after the build finishes, the CPU remains high (2 to 3 cores at 100% on a 8 HT core system) for the java process, even after a few minutes, and without making any code changes (or even touching the VSCode during that period). Disabling auto-build ("java.autobuild.enabled":false) and restarting VSCode, then manually building, the CPU usage returns to close to idle after the build completes (which is what is expected).

Environment

• Operating System: macOD High Sierra 10.13.5 (MacBook Pro retina mid-2012)
• JDK version: 8.0_131
• Visual Studio Code version: 1.25.0
• Java extension version: 0.3.0

Steps To Reproduce

1. On a Mac start up VSCode and make sure java.autobuild.enabled:true (default)
2. Load up a Maven project
3. Let it build automatically; when the build finishes, monitor the CPU usage for the "java" named process.

Current Result

CPU usage remains high and doesn't seem to come down even after a few minutes

Expected Result

CPU usage to come close to idle after build completes

Additional Informations

The only java program running at that time is the plugin:

$ jps -v
18472 Jps -Dapplication.home=/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home -Xms8m
18346 org.eclipse.equinox.launcher_1.5.100.v20180611-1436.jar -Declipse.application=org.eclipse.jdt.ls.core.id1 -Dosgi.bundles.defaultStartLevel=4 -Declipse.product=org.eclipse.jdt.ls.core.product -Xverify:none -Xmx1G -XX:+UseG1GC -XX:+UseStringDeduplication

server.log
Process Sample of java.txt

Commencez par examiner server.log et Process Sample of java.txt, puis reproduisez le rapport avec java.autobuild.enabled activé sur un projet Maven dans VS Code. Comparez le processus Java après les builds automatiques et manuels ; c'est terminé lorsque le CPU revient près de l'état inactif après la fin du build automatique, sans modification du code.