# Huge memory leaks and permanent performance degredation on Windows

**URL:** <https://forum.cursor.com/t/huge-memory-leaks-and-permanent-performance-degredation-on-windows/128549>\
**Category:** Bug Reports\
**Created:** [August 11, 2025, 9:25pm UTC](https://forum.cursor.com/t/huge-memory-leaks-and-permanent-performance-degredation-on-windows/128549 "2025-08-11T21:25:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tones31](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tones31/32/76050_2.png) [@tones31](https://forum.cursor.com/u/tones31)\
**Post date:** [August 11, 2025, 9:25pm UTC](https://forum.cursor.com/t/huge-memory-leaks-and-permanent-performance-degredation-on-windows/128549/1 "2025-08-11T21:25:55Z")

</div>

### Describe the Bug

Love Cursor but never seen anything like this. I have definitely honed in on Cursor being the problem. Here are the two issue I am seeing

- Memory leak. After only a few minutes of use, goodbye all of my RAM, never to be seen again.
- Performance. I like to game during coding sessions. I can’t play anything without constant stutters even after closing Cursor. Must reboot the system.

Anyways, what a great bug report.. I don’t know how to be more helpful.

### Steps to Reproduce

Use cursor  
Do a couple prompts  
Lose memory

### Expected Behavior

Not lose memory

### Operating System

Windows 10/11

### Current Cursor Version (Menu → About Cursor → Copy)

Version 1.4.3  
VS Code 1.99.3

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![tmm1](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tmm1/32/3131_2.png) [@tmm1](https://forum.cursor.com/u/tmm1)\
**Post date:** [August 11, 2025, 9:27pm UTC](https://forum.cursor.com/t/huge-memory-leaks-and-permanent-performance-degredation-on-windows/128549/2 "2025-08-11T21:27:34Z")

</div>

We are working on this. Can you try v1.4.4 via `Cursor Settings > Beta > Update Access: Early Access` ?

---

<div class="post-metadata">

**Author:** ![rebroad](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/rebroad/32/50629_2.png) [@rebroad](https://forum.cursor.com/u/rebroad)\
**Post date:** [August 13, 2025, 12:34pm UTC](https://forum.cursor.com/t/huge-memory-leaks-and-permanent-performance-degredation-on-windows/128549/3 "2025-08-13T12:34:11Z")

</div>

I am also having this issue. Having to quit cursor every 20 minutes or so as all the memory (all 16GB) is used up.

Version: 1.4.5  
VSCode Version: 1.99.3  
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290  
Date: 2025-08-13T02:08:56.371Z  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1  
V8: 13.2.152.41-electron.0  
OS: Linux x64 6.14.0-27-generic

---

<div class="post-metadata">

**Author:** ![tmm1](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tmm1/32/3131_2.png) [@tmm1](https://forum.cursor.com/u/tmm1)\
**Post date:** [August 13, 2025, 1:15pm UTC](https://forum.cursor.com/t/huge-memory-leaks-and-permanent-performance-degredation-on-windows/128549/4 "2025-08-13T13:15:55Z")

</div>

Can you screenshot `>Developer: Process Explorer`

---

<div class="post-metadata">

**Author:** ![tones31](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tones31/32/76050_2.png) [@tones31](https://forum.cursor.com/u/tones31)\
**Post date:** [August 26, 2025, 8:47pm UTC](https://forum.cursor.com/t/huge-memory-leaks-and-permanent-performance-degredation-on-windows/128549/5 "2025-08-26T20:47:11Z")

</div>

It shows low memory usage, like 127 mb  
But of course thats the thing with memory leaks. You don’t see em.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [September 17, 2025, 8:47pm UTC](https://forum.cursor.com/t/huge-memory-leaks-and-permanent-performance-degredation-on-windows/128549/6 "2025-09-17T20:47:16Z")

</div>

Closed on September 17, 2025, 8:47pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
