Cursor crash (OOM)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I got Cursor to crash violently while working on 3 (quite long) AI chats in parallel.

Steps to Reproduce

Unsure. Use Cursor extensively, working on 3 different tasks / AI chats in parallel.

Expected Behavior

No crash

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77 (user setup)
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
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?

Sonnet 4.5 in 2 chats
Composer 1 in 1 chat

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. OOM crashes with multiple chats open can be caused by extensions or very long chat history consuming a lot of memory.

Please try the following diagnostics:

  • Safe mode test: run cursor --disable-extensions from your terminal and use Cursor as usual. Does the crash still happen?
  • Process check: before the crash occurs, press Ctrl+Shift+P → Developer: Open Process Explorer and take a screenshot showing which process is using the most memory.
  • Clear long chats: if your 3 chats are very long, try temporarily clearing the chat history and see if that helps.

Also, please share:

  • Which extensions you have installed
  • How much RAM your system has
  • The approximate length of those 3 chats (number of messages)

Let me know what the safe mode test shows!

1 Like

Thanks, I’ll make sure to take a screenshot next time when I feel Cursor becoming sluggish.
In the meantime:
* Number of messages in the chat: Is there an easy way to check this? I have no idea.
* Extensions: very few

* System RAM: 96GB

Great info! With only 2 minimal extensions and 96GB of RAM, it’s unlikely this is caused by extensions, but the safe mode test will confirm.

In the meantime, to estimate chat length: there’s no built-in counter, but you can scroll through the chat to get a rough sense. Very long chats (100+ messages with large code blocks) can use a significant amount of memory.

When you’re able to grab a Process Explorer screenshot right before the next crash, please share it here along with the safe mode test results. That will help us see which process is using the memory and whether it’s extension-related or a core issue.

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