jhipster / jhipster-ide

An IDE for the JHipster Domain Language

Home Page:https://jhipster.github.io/jhipster-ide

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

VS Code Studio: ServerLauncher process using high CPU

smunir opened this issue · comments

Opending JDL file in VS Code Studio launches ServerLauncher process which consumes almost 100% CPU.

To Reproduce
Steps to reproduce the behavior:

  1. Install Jhipster extension in VS Code
  2. Open JDL file
  3. Check activity monitor for ServerLauncher process
  4. Check that ServerLauncher process is consuming high CPU

Expected behavior
ServerLauncher should not consume this much CPU.

Screenshots
image

Desktop (please complete the following information):

  • OS: macOS Big Sur
  • Version: 11.2.1

yes, sure, but after it has started it takes nearly no cpu power:

image

It kinda gets stuck and doesn't start in my machine and keeps taking 101% CPU. I need to work on a JDL and my Mac is getting too hot because of this :-(

Any workaround would be great

...hm, strange, which JDK version do you use?

you need a Java 11 JDK:

image

I am using https://sdkman.io for managing JDK Installations and had value your pointed and java.home in settings.json set to /Users/shahzad/.sdkman/candidates/java/current. I updated this to /Users/shahzad/.sdkman/candidates/java/11.0.2-open and now I can't see ServerLauncher process in activity monitor. Even setting it back to /Users/shahzad/.sdkman/candidates/java/current didn't make any difference. Looks like just modifying settings.json solved this issue. I can see JDK Language Server started! in status bar, suggestions/templates are working fine, not sure what issues I could face but CPU and fan are happy now. Should I close the issue if we don't need to investigate absence of ServerLauncher in processes list?

if you do not see the ServerLauncher process anymore then it's not working at all...

I am using java over sdkman on a macbook and have no problems.

image

Try this version: AdoptOpenJDK / 11.0.10.hs-adpt

It started a few hours ago again with same CPU percentage. As you suggested I switched to AdoptOpenJDK / 11.0.10.hs-adpt and now it's started taking only 0.2% CPU. We can conclude that this was because of Open JDK. Thanks for your help.