-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very high CPU usage on remote #33
Comments
This is an issue with the underlying groovy language server. I will open an issue with them for you and link it back to here. |
Thanks. I also just noticed it has been running for 1630h before I manually killed it. Also are there supposed to be multiple instances of it running? I think these might be zombie processes. |
@ErikParawell-SiFive These are all really good questions that I wish I had an answer to. I kinda just inherited this thing. I used to have similar issues, but I don't anymore. I think I switched java versions. Let me load up my environment later today and I will see how many processes and stuff are running so we can compare. I will also look at which java version I am running. |
Yeah no worries. I'll try and help out with this issue as much as I can, but if it can't be resolved with a reasonable amount of effort we can drop it. I also noticed that the language server you are using has some pretty recent commits that you may or may not be using in this current release.
|
Updating the LS version that is bundled with the extension is another thing that needs to be done. We used to use the https://github.com/GroovyLanguageServer/groovy-language-server directly but ended up forking it when it took a while to get our bug and features merged. This weekend I will look into either updating the fork https://github.com/DontShaveTheYak/groovy-language-server or just switching back to using the offical LS. |
@ErikParawell-SiFive I have published a new version |
I have this extension installed on a remote machine. I'm not sure why, but it has a very high cpu utilization. It is worth mentioning that this repo I am using is very big, so maybe that's why.
The text was updated successfully, but these errors were encountered: