Cursor 2.2.36 leaks like a sieve

Support Bug Reports
1

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 errors.

Steps to Reproduce

run and use Cursor Client

Expected Behavior

not crash and throw OOM messages

Screenshots / Screen Recordings

image
image1450×1993 237 KB

Operating System

Windows 11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.36 (system setup)
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z
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

For AI issues: which model did you use?

Opus 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

2

I am on MacOS with 64GB RAM and 4TB disk. Cursor used to work PERFECTLY. Since upgrading to 2.2.36, it crashes at least once an hour with error code 5

3

i chose the wrong os when creating this. I’m on Windows 11.

4

Hey, thanks for the detailed report. I see the screenshot with the OOM error -536870904.

Several users are reporting similar issues with version 2.2.36. For diagnosis, could you share:

  1. Open CTRL+Shift+P > Developer: Open Process Explorer - which process is using the most memory before the crash?
  2. Check extensions: Settings > Application > Experimental > Extension Monitor Enabled, then CTRL+Shift+P > Developer: Open Extension Monitor
  3. Try launching with extensions disabled: cursor --disable-extensions from the command line

Let me know the results. This will help the engineering team.

1 Like
5

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

1 Like
6

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.

7

Got it. Also now running without extentions after last crash

8

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.

9

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

1 Like
10

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

11

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 " "} printf(“PID: %s RSS: %.2f MB VSZ: %.2f MB CMD: %s\n”,$1,$2/1024,$3/1024,cmd)}’; done

Example output:
$ 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 " "} printf(“PID: %s RSS: %.2f MB VSZ: %.2f MB CMD: %s\n”,$1,$2/1024,$3/1024,cmd)}’; done

PID: 25702 RSS: 587.00 MB VSZ: 1823336.88 MB CMD: Cursor Helper (Plugin): extension-host [1-3]
PID: 45665 RSS: 671.42 MB VSZ: 1825339.48 MB CMD: /Applications/Cursor.app/Contents/Frameworks/Cursor Helper (Renderer).app/Contents/MacOS/Cursor Helper (Renderer) --type=renderer --user-data-dir=/Users/rlee/Library/Application Support/Cursor --standard-schemes=vscode-webview,vscode-file --enable-sandbox --secure-schemes=vscode-webview,vscode-file,sentry-ipc --bypasscsp-schemes=sentry-ipc --cors-schemes=vscode-webview,vscode-file,sentry-ipc --fetch-schemes=vscode-webview,vscode-file,sentry-ipc --service-worker-schemes=vscode-webview --code-cache-schemes=vscode-webview,vscode-file --app-path=/Applications/Cursor.app/Contents/Resources/app --enable-sandbox --enable-blink-features=HighlightAPI --force-gpu-mem-available-mb=1024 --disable-blink-features=FontMatchingCTMigration,StandardizedBrowserZoom, --lang=en-US --num-raster-threads=4 --enable-zero-copy --enable-gpu-memory-buffer-compositor-resources --enable-main-frame-before-activation --renderer-client-id=4 --time-ticks-at-unix-epoch=-1765608985255660 --launch-time-ticks=310125392062 --shared-files --field-trial-handle=1718379636,r,15967952631763731220,8951569188940678300,262144 --enable-features=DocumentPolicyIncludeJSCallStacksInCrashReports,PdfUseShowSaveFilePicker,ScreenCaptureKitPickerScreen,ScreenCaptureKitStreamPickerSonoma --disable-features=CalculateNativeWinOcclusion,MacWebContentsOcclusion,PlzDedicatedWorker,ScreenAIOCREnabled,SpareRendererForSitePerProcess,TimeoutHangingVideoCaptureStarts --variations-seed-version --vscode-window-config=vscode:c08cdec7-be89-4261-bfc6-e556523ffb3c --seatbelt-client=47
PID: 45815 RSS: 236.17 MB VSZ: 1823343.38 MB CMD: Cursor Helper (Plugin): extension-host [2-1]
PID: 45608 RSS: 172.97 MB VSZ: 1824267.73 MB CMD: /Applications/Cursor.app/Contents/MacOS/Cursor
PID: 45814 RSS: 32.41 MB VSZ: 1823313.77 MB CMD: Cursor Helper: terminal pty-host
PID: 31749 RSS: 24.67 MB VSZ: 1821543.59 MB CMD: /Applications/Cursor.app/Contents/Frameworks/Cursor Helper (Plugin).app/Contents/MacOS/Cursor Helper (Plugin) /Applications/Cursor.app/Contents/Resources/app/extensions/markdown-language-features/dist/serverWorkerMain --node-ipc --clientProcessId=25702

12

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 $ …

+ ~

Missing statement body in do loop.

+ CategoryInfo          : ParserError: (:) \[\], ParentContainsErrorRecordException

+ FullyQualifiedErrorId : MissingOpenParenthesisAfterKeyword
13

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 manager says it gets to about 6.2gb then crashes, I’ve got 32gb and half is free at that point.

14

TY, was considering trying 2.2 again (2.1.50 is okish).

Well, will wait for 6.0