Memory Leak on MacOS. Using +7gb Memory on Empty Project

[kyle-tennison]

When I open the parent dir of any rust project, it looks like there is some sort of memory leak; the "rust-analyzer" icon spins indefinitely as memory racks up.
I'm on macOS Ventura 13.1 on M1 (macbook air 2020). I have no issues whatsoever when I open the crate's directory directly.

I really like this plugin, so I hope this helps. Good luck!

rust-analyzer version: v0.4.1773 (plus whatever the main release is)

rustc version: rustc 1.73.0 (cc66ad468 2023-10-03)

relevant settings: Everything vanilla. No env vars set.

[kyle-tennison]

The steps to recreate

1. mkdir parent_dir
2. cd parent_dir
3. mkdir project_dir
4. cd project_dir
5. cargo init
6. code .. (open vscode in parent dir)
7. open main.rs in vscode
8. wait a minute for memory to rack up

[lnicola]

Can't reproduce on Linux.

[Veykril]

Can't repro this on windows either

[DrewMcArthur]

@Veykril is this something that got fixed or just was not reproducible? i'm getting around 40gb of memory usage on macOS, with an M2 mbp. 16gb of actual ram, so it's filling up all my swap too. this has been happening pretty consistently working on a specific project, most recently when i changed git branches. I had also changed to the prerelease version, and had the same issue. happy to help try to find the source of this.

Sample of rust-analyzer.txt

edit; i think it has to do with the format-on-save functionality. i save a file, and sometimes it hangs, i get a notification in vs code that it's trying to run the formatter before saving. i have to cancel that to save the file, and then the memory usage quickly balloons. here's a screenshot.

[Veykril]

Not reproducible, if you have a leak problem please update to the latest release and check again

[kyle-tennison]

@Veykril , the example I provided may indeed be reproducible—just not on other OS's. The issue is still present on the latest release, and considering somebody else has bumped into the same issue on MacOS, it might be a mac-specific bug. I appreciate your help though.

@DrewMcArthur , if you're open to it, it would be awesome if you could let us know if the example in the original post will cause a leak for you too; this way, we can verify the issue is reproducible on other mac machines.

[Veykril]

Then someone with a mac will have to investigate as I don't have such a machine.

[DrewMcArthur]

i think #16935 fixed my issue but i'll see if i can reproduce