Cursor 0.46.7 crashes frequently on Windows - OOM

Cursor v46.7 crashes every 5-10 minutes for me. Paid Pro user.

The error message on crashing refers to “OOM” which I assume means “out of memory”.

I have 32GB of RAM and have closed as many other applications as I can.

I note that Process Explorer shows that Cursor is regularly using 2.7GB of memory, and occasionally jumps up to 3.5GB+ for a few seconds.

Version: 0.46.7 (user setup)
VSCode Version: 1.96.2
Commit: 3611c5390c448b242ab97e328493bb8ef7241e60
Date: 2025-02-27T07:28:03.958Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

Hi, if you have time to debug, I’d love to setup a google meeting and try to reproduce and debug/fix the memory issue you’re seeing.

Yes, sure @Zackh1998 . Ping me directly and we can set something up.

Same here. Out of memory after about 5 minutes.
64 GB DDR5 RAM.
Win 11

Same for me on Mac. I’ve had earlier version open for many hours. Just today cursor has crashed with this error three times in as many hours.

@adisolar @Rednas I’ve managed to resolve the issue - or at least for the moment.

I did the following:

  1. Updated to 0.46.7
  2. Did a restart on my laptop
  3. Restarted Cursor

At that point, my (very large) Composer chat had disappeared. Which is annoying. However, it seems the size of my Composer chat may have been the underlying cause of at least some of the OOM issues.

My memory usage is significantly down compared to before and I haven’t had an OOM error in over a day.

You might try starting a new Chat and see if that helps.

Thanks for the info, however, I did all that. Started the program, immediately started a new chat - triggered the crash immediately. After restart the old chat window was restored so it gave me the chance to A>B test this issue. Leaving the “old” chat window there, triggered the crash after about 5-7 minutes. Opening a new chat window triggered the crash almost immediately.

0.46.8 solved the issue for me

Just found this thread. I’m having similar issues, but I can also rule out the chat being too large as the culprit: