search

neoclide / coc-java

Java extension for coc.nvim
Eclipse Public License 1.0
449 stars 40 forks source link

java process is not killed after quiting nvim #49

Open vcfvct opened 4 years ago

vcfvct commented 4 years ago

Seems the java process does not exit after vim quit. Is there any lifecycle hooks to ensure the resource getting released?

/Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home/bin/java -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m -Dfile.encoding=utf-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /Users/myUser/.gradle/wrapper/dists/gradle-3.5-bin/a9dfgtj5kwo69rnsu3ha320bn/gradle-3.5/lib/gradle-launcher-3.5.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 3.5

System: MacOS Mojave nvim: v0.4.2 Screen Shot 2019-10-16 at 1 12 27 PM

Thanks for the awesome coc.vim!

patrickpichler commented 4 years ago

Gradle is starting a background daemon for faster compilation times. So if you execute lets say gradle build gradle will start a daemon as well. So this is not really related to coc-java.

Heres a link to the official gradle documentation https://docs.gradle.org/current/userguide/gradle_daemon.html

vcfvct commented 4 years ago

@patrickpichler do you mean the jdt language server is starting this? FYI I did not run any gradle command, just nvim xxxx.java and that process will be brought up.

patrickpichler commented 4 years ago

Exactly. jdt uses the eclipse gradle plugin (if I'm not mistaken) and this starts the gradle daemon to get informations about the build.

chemzqm commented 1 year ago

Should be fixed on recent version of coc-java, try upgrade coc.nvim to latest release and coc-java to version 1.14.0.