-
-
Notifications
You must be signed in to change notification settings - Fork 56
Description
What version?
0.49.4
Which command?
No response
What happened?
Hey guys, (maybe) a niche issue here. I'm not sure if this is an issue for Zed or proto - I apologize if this is the wrong place for it.
When opening Zed and opening a file, it likes to download binaries for the LSP / linting / etc. However, this process seems to hang and it leaves a proto process hung in Activity Monitor. I suspect this is because Zed probably wants to spawn node or npm to download the relevant binaries.
This proto process will remain here even after Zed is quit and will continue consuming CPU. If you spawn multiple instances of Zed and open a file so it downloads LSP data, there will be multiple instances of proto consuming CPU (seen below after 3 iterations).
I suspect this may be resolved by me defining a ~/.prototools and setting a node / npm version and installing those. At the moment, only pnpm is defined in there.
Edit: Unfortunately defining those and installing node / npm with those versions did not resolve the issue.
Trace logs?
No response
Operating system?
MacOS
Architecture?
arm64