-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Several node processes launches every time I open the app and cause 2+GBs of RAM usage #16430
Comments
I just saw consumption of ~1.4GB, well above the typical. Quit the application and reopened a single project, back up to 667MB. macOS 14.6.1 |
Also a thing that I've noticed on a fresh start RAM usage of the app is around 120MBs after couple of hours I got around 700MBs |
A few days ago I have left my Zed open for a few hours while my MacBook was in lock screen and when I came back, Zed was consuming 32GB of ram (my MacBook only has 8GB so you can imagine what happened). I noticed that it starts consuming more and more RAM and it comes from node process most of the time. Sometimes I have to reload Zed to keep RAM usage low. |
I am experiencing the same issue when opening a Node.js app with around ~8k LOC of Typescript (The size of the folder is relatively large at 1GB due to dependencies). I am experiencing the same issues using VSCode (which is why I also linked this issue in the issue i opened on their Github repo) - since afaik Zed uses vtsls which if i understand correctly is just a wrapper around VS Code's implementation of the Typescript LSP, I assume the real problem is somwhere in the LSP itself. In my case, I am basically stuck in an infinite |
This happens with me when i use the |
I now removed |
I tried doing the same, unfortunately, no change. |
It worked for a while for me, but now I have the same issue again. 😢 |
Can checkout this workaround, it reduce the memory usage a lot in my case. #18698 (comment) |
@chungweileong94 thanks for providing a workaround, but unfortunately it didn’t help |
In my case, I guess I have a big project. I've tried to disable Copilot and same issue |
Check for existing issues
Describe the bug / provide steps to reproduce it
I would that say this is a clarification if the behaviour is intended to work like this, rather than a bug report, anyway:
Opening the app with my Next.js project I see this in the Activity Monitor:
No local things are running, I've just opened the app and two node processes already taking 2.5 GB of RAM. Also, if I'm not mistaken Zed installs its own node in the system even if I have one already?
So, the question: is Zed preloading node on the app launch or there some other reasons?
Environment
Zed: v0.149.1 (Zed Preview)
OS: macOS 14.6.1
Memory: 16 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
Zed.log
The text was updated successfully, but these errors were encountered: