OOM problems persist in Cursor 2.3 despite available memory

[Work_Dre]

OOM problems again!

I don/t understand this. My system has 64GB. Cursor typically uses 4GB. why doesnt it use what’s available? current environment:

Version: 2.3.29 (system setup)
VSCode Version: 1.105.1
Commit: 4ca9b38c6c97d4243bf0c61e51426667cb964bd0
Date: 2026-01-08T00:34:49.798Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

I estimate around 60%-70% of my token use is rework due to cursor crashing. Cursor needs to make this right by not charging for extra work. If not, you actually have a disincentive to fix the problem.

[Work_Dre]

another crash:

[Work_Dre]

Another Crash. Another duplication of work. more wasted tokens.

[Work_Dre]

another crash. more wasted tokens.

[andrewh (Andrew Milich)]

Looking into this. Apologies

[noor (Noredeen Al-Zu'bi)]

We are sorry about this @Work_Dre. Is there any chance you can get us an export of the cursor process history? you can access that by opening the command palette via ctrl-shift-P and running > Developer: Open Process Explorer. there will be a memory history tab, where you can click a save button in the top bar.

[Work_Dre]

This is what i have:

[noor (Noredeen Al-Zu'bi)]

If you have privacy mode turned off, another thing to try: from the same command palette, run Developer: Capture and Send Debugging Data.

[Work_Dre]

Developer: Capture and Send Debugging Data command was run. Althought i dont know where the infromation was sent? What else do i need to do?

[Work_Dre]

more oom errors:

[Work_Dre]

More errors. more wasted tokens.

[Work_Dre]

Still broken. how can you run out of memory with 40G of computer memory unused?

Version: 2.3.34 (system setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

[Work_Dre]

Developer: Capture and Send Debugging Data command was run. Although I don’t know where the information was sent? What else do I need to do? this needs to stop.

[Work_Dre]

more of the same. this is ridiculous.

[Work_Dre]

Am I the only user with this pervasive problem?

[Work_Dre]

[Work_Dre]

[Work_Dre]

[Work_Dre]

16 of these today, so far.

[Work_Dre]

**

What can i do to help you solve this? Now using V 2.3.35

**