Cursor-server using massive memory

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.

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


Hi @aagatti

Same here: