For any one trying to resolve the problem, if this happens while you are starting cursor inside a docker container, don’t try to open the root folder in the container, open only the specific folder you are trying to work with, this resolved it for me.
This still happens. It is painful.
Same issue here. Long chat in yolo mode. Can you fix this issue ? (MacOS 15.3.2 (24D81))
It is using 1-1.5GB of RAM, but using up 110/120% of my CPU.
I am running MacOS Version 14.5 (23F79), 2021 MacBook Pro with Apple M1 Pro Chip.
cursor --disable-extensions this fix is also not working when it comes to CPU.
It is Generating a response for past 15-20 mins -
Activity Monitor -
I love Cursor to bits, but this was my final straw between no intelligent memory in chats, looping eating my credits, Ask mode eating my credits by trying to make changes (??? just add context) and various issues. I adore this software but there are just too many things that haven’t been addressed in months. The only option is pay the competitor more in favor of something refined.
Memory issue is affecting me too! Causes my Mac M1 Pro 16GB RAM to freeze out each time I run the tests.
I’m not able to do anything for about 10 min whilst it completes 1200 tests. Started happening recently. Before it would do all 1200 in under 3min.
Started to become annoying! Relieved to see I’m not alone with these issues. Hopefully they fix it soon with AI!
I have the same issue. Cursor take between 10GB - 15GB on my M2 Pro 16GB. Have to force macbook to turn off. Crashes every day at work. I didn’t have this issue before the recent version.
Cursor Version: 1.0.0
VSCode Version: 1.96.2
@Nick93 could you file a full bug report please? This thread is over a year old and for different Cursor version.
With more info the Cursor Team can look into what is causing the issue
@Wuntenn could you please create a separate bug report? Your issue happens when you run tests so it may have to do with the test tool you use and not necessarily be a Cursor issue.
But to review the issue more info is needed. Please in separate thread.