# Global Cursor IDE resource leaks

**URL:** <https://forum.cursor.com/t/global-cursor-ide-resource-leaks/172028>\
**Category:** Bug Reports\
**Tags:** performance\
**Created:** [September 17, 2026, 1:17pm UTC](https://forum.cursor.com/t/global-cursor-ide-resource-leaks/172028 "2026-09-17T13:17:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anoncoder555](https://avatars.discourse-cdn.com/v4/letter/a/b2d939/32.png) [@anoncoder555](https://forum.cursor.com/u/anoncoder555)\
**Post date:** [September 17, 2026, 1:17pm UTC](https://forum.cursor.com/t/global-cursor-ide-resource-leaks/172028/1 "2026-09-17T13:17:27Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Cursor is responsible of 99% of my OOM errors of my system. Agents tab consumes less memory than IDE but still causes OOM errors all the time. I believe every UI integration isnt properly UI updated with a lot of bottlenecks and lots of data in memory that could have been cleared

### Steps to Reproduce

Run cursor and do anything

### Operating System

Linux

### Version Information

Cursor IDE 3.20

### For AI issues: which model did you use?

Auto

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [September 17, 2026, 5:19pm UTC](https://forum.cursor.com/t/global-cursor-ide-resource-leaks/172028/6 "2026-09-17T17:19:55Z")

</div>

Hey @anoncoder555, thanks for the report, and sorry about the OOM trouble.

One thing to check first: the Cursor installation we see reporting from your machine is on version **3.9.16 (a build from late June), not 3.20**. Could you open Cursor → Help → About and confirm the version? On Linux, .deb and .rpm installs do not update themselves, so it is easy to end up on an old build without noticing.

A lot of memory work has shipped since 3.9, especially for the Agents window, so please update to the current release first: grab the latest from [Cursor · Download](https://cursor.com/downloads) (the AppImage keeps itself up to date; for .rpm/.deb you need to install the new package or use our apt/yum repository). Then use it for a day or two the way you normally would.

If it still runs out of memory on the new version, this would help us pin it down:

1. When memory starts climbing, open Help → Open Process Explorer and tell us which process is the big one (renderer, extension host, or something the agent launched like a build or dev server).
2. In the Agents window, open the command palette (Ctrl+Shift+P), run “Capture and Send Debugging Data”, tick “Renderer heap snapshot” (leave the defaults ticked), and press Enter. Please do this while the Agents window is around 1.5 to 2.5 GB, not after it has already stalled.

Let me know how this goes and if you see any improvements after updating. Also let me know if you have any trouble updating as I can walk you thru the steps for how to do so on Linux.

---

<div class="post-metadata">

**Author:** ![anoncoder555](https://avatars.discourse-cdn.com/v4/letter/a/b2d939/32.png) [@anoncoder555](https://forum.cursor.com/u/anoncoder555)\
**Post date:** [September 21, 2026, 4:06pm UTC](https://forum.cursor.com/t/global-cursor-ide-resource-leaks/172028/7 "2026-09-21T16:06:25Z")

</div>

cursor --version  
3.21.16  
8ae78e8eee1e63479c7e0504b664bc0a80c68000  
x64

 ![Capture d'écran_20260921_174132](https://us1.discourse-cdn.com/cursor1/original/3X/e/6/e675af0834c0e3ee3be5c073da5c9838305fb406.png)

 ![Capture d'écran_20260921_180410](https://us1.discourse-cdn.com/cursor1/original/3X/a/7/a73112d42098279d82267e3b2d6a4765f1e97ea6.png)
