Where does the bug appear (feature/product)? Cursor IDE Describe the Bug Since updating to 2.2.36 Cursor crashes and throws an OOM all the time. The only way to get it back is to reboot my computer. 17 times in the last 4 hours. This must be fixed. 2.2.20 had its quirks but not ridiculous OOM error…

Process Explorer only shows the current state - it doesn’t keep history after a crash. To capture the data, you need to open Process Explorer before the crash happens and keep the window open to monitor it.

Got it. Also now running without extentions after last crash

Disabling extentions no help. Still ran OOM. Failed to collect process explorer as it reset after crash. Not sure how to capture something before it happens.

Could you try updating to 2.2.43? We’re progressively patching a ton of longstanding memory leaks and instability. Apologies.

I have been on 2.2.43 for several minutes. Still scrashing due to OOM.

Hello, Next time it’s dragging could you please run this in your terminal and share the output? Let’s see how mem it’s holding… for PID in $(ps aux | grep -i cursor | grep -v grep | awk ‘{print $2}’); do ps -p “$PID” -o pid=,rss=,vsz=,command= -ww | awk ‘{cmd=“”; for(i=4;i<=NF;i++){cmd=cmd $i " "}…

RESPONSE: At line:1 char:4 + for PID in $(ps aux | grep -i cursor | grep -v grep | awk {print $2}) … + ~ Missing opening ‘(’ after keyword ‘for’. At line:1 char:74 + … (ps aux | grep -i cursor | grep -v grep | awk {print $2}); do ps -p $ … + …

Same issues here too. I’ve realized that if I do smaller edits and then ask it to ask me before continuing then then accept the files. Then tell it to continue from there, the crashes don’t happen. When doing larger edits, every time it’s crashing and unable to retrieve the memory process. My task…

TY, was considering trying 2.2 again (2.1.50 is okish). Well, will wait for 6.0

Cursor 2.2.36 leaks like a sieve

Support Bug Reports

Work_Dre (Work Dre) December 19, 2025, 6:00pm 5

How do I bring up process explorer when Cursor has crashed? It shows no history.

1 Like

Topic		Replies	Views
OOM Cursor - The window terminated unexpectedly (reason: 'oom', code: '-536870904') We are sorry for the inconvenience. You can reopen the window to continue where you left off Bug Reports	12	403	February 5, 2026
Cursor consuming massive amounts of memory and compute Bug Reports	50	16031	March 19, 2026
Constant OOM code 536870904 with latest update Bug Reports installation , performance , crashes	11	509	March 6, 2026
Keeps crashing while agent running in long session Bug Reports terminal , wsl , performance , crashes , linux	10	196	March 1, 2026
Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans Bug Reports plan-mode , performance , crashes	50	3098	April 7, 2026

Cursor 2.2.36 leaks like a sieve

Related topics