Always popup this alert :memory use large than 4000MB

Support Bug Reports
,
1

After using it for a period of time, it will crash and restart，I can hardly use it
image

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (Signing in to Cursor, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

4

Where does the bug appear
it appears in editor

Describe the Bug
restart my pc and open cursor, use for a short time,than popup a alert: using memory large than 4000MB，I cant click any button in cursor

Operating System
win10

Version Information
Version: 3.22.7 (system setup)
VS Code Extension API: 1.128.0
Commit: 37076c6c3f9e253c0fa2305197e45befd13a2260
Date: 2026-09-24T05:01:24.589Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor?
Cursor is unusable

zheng_gu (zheng gu) 6

image

7

Hey, thanks for the report and the screenshot. This is an issue we’re tracking. On some Windows builds, during long Agent sessions, the window’s memory usage keeps growing until the window is closed and restarted.

For now, these workarounds usually help:

  • Start a new chat for each task instead of keeping one long chat.
  • When you see the warning Cursor is using a lot of memory, press Ctrl+Shift+P, run Developer: Reload Window, and keep working. Reload frees memory before the window crashes.

To help us narrow down the cause, please try this once and tell us what you see:

  1. Fully close Cursor, including from the system tray, then open it again.
  2. Open Help > Open Process Explorer and keep that window open.
  3. Use Agent like you normally do.
  4. When the memory warning appears, check which row in Process Explorer has the highest usage, for example window or extensionHost, and note the exact number.
  5. Press Ctrl+Shift+P, run Capture and Send Debugging Data, and select renderer heap snapshot if it’s offered.
  6. If the window closes, write down the exact message, for example The window terminated unexpectedly (reason: ‘oom’, …).

Send us the result from Process Explorer and the crash message text. Let me know how it goes.

8

it appears many times today :sleeping_face:

9

Got it, it triggers a lot and it really gets in the way. We’re tracking it. On some Windows builds, during long Agent sessions the window’s memory keeps growing until the window is closed and restarted.

What helps right now, before a restart:

  • As soon as you see the warning “Cursor is using a lot of memory”, press Ctrl+Shift+P then run Developer: Reload Window. Reload frees memory before the window crashes, so you can keep going.
  • Start a new chat for each task instead of continuing one long chat.

To help us narrow down the cause, please try this once and tell me what you see:

  1. Fully quit Cursor, including from the system tray, then open it again.
  2. Go to Help > Open Process Explorer and keep that window open.
  3. Use Agent like you normally do.
  4. When the memory warning shows up, check which row in Process Explorer has the highest usage like window or extensionHost and write down the number.
  5. Press Ctrl+Shift+P then run Capture and Send Debugging Data and pick renderer heap snapshot if it offers it.
  6. If the window closes, copy the exact message text like The window terminated unexpectedly (reason: 'oom', ...).

Send the Process Explorer line and the crash message text. That’ll help a lot to narrow this down. Let me know how it goes.