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

[formatter] - Stays resident in memory taking ~ 1.4 GB on macos #20478

Closed
FrankC01 opened this issue Dec 1, 2024 · 4 comments
Closed

[formatter] - Stays resident in memory taking ~ 1.4 GB on macos #20478

FrankC01 opened this issue Dec 1, 2024 · 4 comments
Assignees

Comments

@FrankC01
Copy link

FrankC01 commented Dec 1, 2024

After shutting down VSC, move-analyzer is staying resident in memory consuming copious amounts of memory.

@stefan-mysten
Copy link
Member

Thanks for the report @FrankC01. We'll have a look asap.

@awelc
Copy link
Contributor

awelc commented Dec 1, 2024

Will try taking a look but it's more of a process management issue than a problem with move-analyzer itself (happens as well with rust-analyzer as well which is an LSP implementation for Rust). I realize it's not ideal, but I had to killall Rust analyzer quite a few times myself, and killall move-analyzer should do here in a pinch as well ..

@melonges
Copy link
Contributor

The same problem, the reason is the vscode plugin, which does not terminate the analyzer before finishing. Or a minimum check on startup if it's already running

Image

@FrankC01
Copy link
Author

FrankC01 commented Jan 21, 2025

So, as this is not a plugin issue (but rather a somewhat sloppy VSC feature ) I'm closing.

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

No branches or pull requests

4 participants