Skip to content
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

Possible memory leak #235

Open
uniks37 opened this issue Jun 26, 2024 · 1 comment
Open

Possible memory leak #235

uniks37 opened this issue Jun 26, 2024 · 1 comment

Comments

@uniks37
Copy link

uniks37 commented Jun 26, 2024

The plugin might be causing huge memory leak. I have been experience the memory leak since past few weeks where the plugin takes up all the resources by spamming the jvm instances. Uninstalling the plugin, however, recovers the system CPU load and frees up memory.

@nvuillam
Copy link
Owner

@uniks37 VsCode Groovy lint relies on npm-groovy-lint, who launches a local server via JVM, then interrogates it via HTTP calls

I always noticed that CodeNarc (behind npm-groovy-lint) has a heavy memory usage... except creating the local server, I never found a real solution as I'm not java expert

Would you know how to detect from where the memory leak is from, so we could fix it (or maybe directly in CodeNarc) ?

cc @stevenh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants