After updating to 2.6.11, I noticed right away that the program was running awfully slow, after a couple of prompts and basic operations RAM usage skyrocketed to 5GB+ (and climbing lol) with CPU usage hovering around 20-30% which points to some sort of memory leak.
Killing the process via task manager and a fresh restart to the welcome window “fixes the issue”, HOWEVER reopening the workspace (that has git history and a couple of active chats with agents) starts leaking memory again, the leak is so severe I can barely get to the built in process explorer without cursor crashing.
Version: 2.6.11 (user setup)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045
FOLLOW-UP: The culprit seems to be an agent mode chat with Opus 4.6 (thinking), selecting that tab (or booting Cursor with that tab selected) immediately inflates the RAM usage and starts leaking heavily. Switching to a different agent tab, closing the entire program and re-starting with the non-problematic agent tab fixes the issue.
Note: some of the information above is copy and pasted verbatim from here because it flew under the radar: https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/22