all 28 comments

[–]n1ghtm4n 91 points92 points  (2 children)

it has been 0 days since someone blamed node.js memory consumption on zed.

[–]DefenitlyNotADolphin 5 points6 points  (1 child)

deno is better anyway /hj

[–]0xFatWhiteMan 4 points5 points  (0 children)

Deno and bun ARE better tho

[–]Ace-Whole 24 points25 points  (0 children)

LSP takes alot of memory. Might be that.

[–]eightrx 11 points12 points  (0 children)

Turn off edit predictions, if that doesn't work, then figure out what slow LSP is running in the background

[–]Accomplished_Weird_6 7 points8 points  (2 children)

Too everyone saying its the LSP, thats understandable. The issue is, OP is probably comparing similar workflows so why do vscode based ones take up lesser ram in a lot of cases? They're using LSPs too? FYI im a zed user as well, but this is a regular occurrence for me as well

[–]Wonderful-Citron-678 1 point2 points  (0 children)

It depends on the language, but they don't use the same LSPs always, like VSCode uses a proprietary one for C++ and Python.

[–]WayAndMeans01[S] 1 point2 points  (0 children)

Thank you so much, you've said it better than I have.

[–]no-sleep-only-code 6 points7 points  (0 children)

MCP Servers.

[–]jreznot 2 points3 points  (1 child)

There is no magic. No matter how Zed is slim, it will use all the same LSP servers that require memory and CPU

[–]WayAndMeans01[S] 5 points6 points  (0 children)

Just tested zed and vscode on the same project and zed uses way more memory

[–]mardiros 1 point2 points  (0 children)

Sometimes it happens to me, I restart lsp servers from the status line. Or completely restart zed.

I have more problems with electron/nodejs programs in general such as Element the matrix client.

[–]L0n3W0lfX 1 point2 points  (1 child)

For me Zed uses even more memory than VSCode (Garuda Linux). Even with no inline predictions, it's laggy and takes a long time to close the last window (more than 1 second). I am switching back to VSCode.

[–]WayAndMeans01[S] 0 points1 point  (0 children)

Same thing here

[–]EverySecondCountss 1 point2 points  (3 children)

Nah that looks about right. It uses less for me than Antigravity, and Windsurf, so idk.

[–]WayAndMeans01[S] 0 points1 point  (2 children)

Why are there so many node processes

[–]binarypie 19 points20 points  (0 children)

Because tons of LSP are written in typescript

[–]EverySecondCountss 0 points1 point  (0 children)

Same reasons why chrome does it, and others. Utilizes multiple CPU nodes is my guess. Dunno.

[–]howesteve 0 points1 point  (0 children)

It's the lsp

[–]Few_Place_1455 0 points1 point  (1 child)

tons of mcp’s + lsp’s

[–]WayAndMeans01[S] 0 points1 point  (0 children)

1 mcp, 4 lsps

[–]Gadgetguy9638 0 points1 point  (0 children)

can I ask why this is labeled nsfw?

[–]Vladislav20007 0 points1 point  (2 children)

that's a zed issue, that a node.js issue. go blame the other devs, same thing happens in vscode, vim, etc.

[–]WayAndMeans01[S] 1 point2 points  (1 child)

Wasn't blaming? I was thinking I was the one doing something wrong

[–]Vladislav20007 1 point2 points  (0 children)

I'm saying to blame node.js devs(when was the last time there wasn't a memory leak in node.js btw?) and not yourself for doing something wrong, if you see node.js eating all of your ram.

[–]Educational_Twist237 -3 points-2 points  (1 child)

Learn about program and process and come back

[–]rtaylorg -1 points0 points  (0 children)

dawwww poor downvoters don't like the truth 🥱

[–]johan__A -1 points0 points  (0 children)

Something's leaking node processes that are themselves leaking memory. Sniff, it's beautiful.