Our compute cluster all of a sudden got dragged to a halt. It looks like cursor (and vs code) are launching 5-10 processes each with 40+gb virtual (and sometimes resident) memory. Anyone experiencing anything similar? Maybe this is a recent update to both cursor and vscode?
Thanks!
Anthony.
Hi @aagatti
Same here:
Thanks! We’ll look into it.
I switched from vscode to cursor, and my server crashes very often. Then I switch back to vscode and my server never crashes! seems like cursor is the cause
I have the same experience, actively using cursor constantly crashes my ec2 instance, so I stopped using it for a week to test with vscode and no crashes happened.
This is still happening to me as well. It spawns endless cursor related Node instances until my server crashes.
One month later - the same for me. AI is supposed to save me time - and yet i’ve spent more than a day troubleshooting why EC2 instance kept going offline until I discovered it was Cursor Server launching tons of Node processes filling the memory and crashing the server.
@deanrie - you pointed something out before, but that didnt seem to solve this and its still an issue.
Our research group is having the same issue mentioned by others. We have a 64 CPU core 128 GB server, but it is being taken down by all of the node processes launched by cursor.
Others seems to reliable report that vscode is not an issue, its only cursor.
Any thoughts on what can be done here?
Can you run view the Process Explorer, as that shows what is using up your resources? It usually comes down to an inefficient extension that causes the issues.
Thanks @danperks - Im looking at my current setup and there is not a ton at the moment. However, this is an issue from most all users of a cluster - we are all doing different research, different libraries, repositories, etc. So, it seems like more widespread issue.
I’ll make sure to bug people as we see major usage and get them to report. I’ll report back if we see any one particular issue reoccuring
Hello,
I’m using Cursor 0.46 and when connecting to ssh on a Ubuntu server i have seen that the .cursor-server processes are configured with a huge amount of Virtual Memory … 74GB for me while my server has only 32GB.
The amount of RAM used is constantly growing and i’m afraid it could go wrong.
Is it an issue from VS Code or something with Cursor ? is it possible to configure the maximuml amount of RAM the cursor-server can consume ?
See the screenshot, first 3 processes are .cursor-server
