Cursor-server using massive memory

[aagatti]

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.

[mouratoglou]

my macbook m1 14’’ was burning hot.
check the screenshot curzon using 99%

[deanrie]

Hi @aagatti

Same here:

Cursor using 99% cpu, crashes, can't save files

Hi @mouratoglou Try this: And this:

[aagatti]

Thanks! We’ll look into it.

[darius]

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

[oscarlz]

@darius

eems like cursor is the

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.

[KevinAHM]

This is still happening to me as well. It spawns endless cursor related Node instances until my server crashes.

[dshepherd]

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.