Computer exhaustion when using Java

[abique]

Relevance Confirmation

• I confirmed that this is not an issue with the Eclipse JDT Language Server itself

What happened?

Zed did start thousand of java instances, leading to quick resource exhaustion.

I tried zed on a large java project using gradle.

What did you expect to happen?

Not crash my computer by using all the cpu and ram.

[valentinegb]

Hi! Super sorry I'm so late to address this, I was super busy for a week and then I got sick for another week ^^'

Firstly, can you open the project fine in VSCode using the Language Support for Java(TM) by Red Hat extension? That extension uses the same language server that this extension for Zed uses, so if that works then we know it's probably not the fault of the language server.

[abique]

No worries.

I've never had great success with vscode either, but zed was worse.
Intellij works fine though.

[valentinegb]

IntelliJ uses a different, in house, language server, I'm pretty sure. You might want to bring up this issue with the JDTLS devs then.

[abique]

I feel too lazy for that sorry.

[swpalmer-cl]

This does not occur with VSCode and the Language Support for Java(TM) by Red Hat extension which only results in two java processes as expected.

[swpalmer-cl]

For some reason this plugin starts a Gradle daemon for every Gradle version ever used even though all but one of them are relevant to the project being opened..

[francescodedomenico]

@valentinegb Hello, it is not a JDTLS bug per se.

I can confirm this is happening to me too and won't happen in vscode, and there's a reason for that.

Zed process on windows (alongside it's child process with jdtls) seems to be kept alive even if we close every editor window.
When you do reopen zed editor in a java project a new jdtls process is spawned as an independent process (not a child process anymore)

After the first re-open

After the second re-open

Zed process keeps staying on and new jdtls independent processes keeps spawning, so this is either a Zed editor problem or an extension one.

[tartarughina]

Could this issue be bound also to how JDTLS is firstly spawned? I see that not only JDTLS keeps running but also the node process for the proxy