Cursor 2.x.x leaks like a sieve

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Pervasive OOM error thrown in every version of Cursor I’ve used. Creating a new Topic since last one referred to an old version of Cursor and this problem transcends versions. I have 64 GB of memory and cursor typically uses ~ 4G. absolutely no reason to throw OOM errors when it is not an OOM case. The screenshots are below. these are from an hour’s use this morning.

image
image1191×488 43.6 KB

image
image1345×557 53.5 KB

image
image1695×813 43.2 KB

image
image1257×631 42 KB

image
image1309×613 36.3 KB

image
image1230×611 35.6 KB

Steps to Reproduce

Use Cursor IDE

Expected Behavior

Not throw OOM Errors

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

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

For AI issues: which model did you use?

Opus 4.5

Additional Information

This wastes my tokens. I expect a token credit unit Cursor fixes the problem.

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
4

Hey, thanks for the report. I see you created a new topic about the same issue as Cursor 2.2.36 leaks like a sieve.

The team is already working on this issue. A team member confirmed that in your previous topic on January 9. We’re patching a lot of memory leaks.

User @Nathan_Hunter also mentioned in your previous topic that making smaller edits and confirming them can help avoid crashes.

5

I have the exact same issue, same code error, fresh query in agent AUTO, cursor stuck at Planning Next Steps, then memory starts to raise 100-200 mb every second until OOM. This happens every time, cursor cannot be used anymore, what options are there?

1 Like
7

Same issue here and can’t reopen my project.