Over the past month, the performance of the Cursor IDE has noticeably deteriorated. After some use, the program suddenly freezes (most often after the computer wakes from sleep mode): the IDE stops responding to input and cannot be closed. It inexplicably consumes all available RAM (I have 32 GB of DDR5)—even with only the browser and the IDE itself running (and no active agents)—and a system reboot is the only fix. Subsequent IDE updates have not resolved the issue.
Steps to Reproduce
Just couple hours of usage, mostly after the computer wakes from sleep mode
Expected Behavior
There are no freezes or unexplained and massive RAM usage—unlike the situation about a month ago.
Hey, thanks for the detailed report. Freezes where RAM gets fully eaten after waking from sleep definitely aren’t expected. To figure out which process is taking the memory, we’ll need a couple things from you. Right now you have Privacy Mode enabled, and that prevents some diagnostics from being collected automatically, so we’ll need you to grab them manually.
Catch the process while memory is growing:
Use Cursor normally until you notice memory climbing or things start slowing down, before it fully freezes.
In Cursor: Help → Open Process Explorer, sort by Memory click the column header, then take a screenshot of the top rows including the Name and CPU columns.
Also open Task Manager Ctrl+Shift+Esc → Details tab → sort by memory → take a screenshot of the top rows.
Let us know how many Cursor windows were open at that time.
Check if an extension is the cause:
Restart Cursor, open Extensions Ctrl+Shift+X, then in the top “…” menu choose Disable All Installed Extensions.
Work like that for a few hours, including a sleep/wake cycle, and tell us if memory still grows and if the freeze happens again after waking.
If it happens again, collect a dump:
Open the Command Palette Ctrl+Shift+P → run Capture and Send Debugging Data with default settings. With Privacy Mode on, it’ll save a zip locally and show the path. Please attach that zip here.
With the screenshots and the zip we can tell what’s growing renderer, agent-exec, or a third-party extension host, and go from there. Let me know how it goes.