Cursor keeps crashing - 2.6.11

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After some time coding, Cursor crashes and shows a window:
“The window terminated unexpectedly (reason: ‘crashed’, code: ‘5’). We are sorry for the inconvenience. You can reopen the window to continue where you left off”.

Steps to Reproduce

Just open Cursor and start coding

Expected Behavior

Cursor should not crash

Operating System

MacOS

Version Information

Version: 2.6.11
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

Yes - Cursor is unusable

6 Likes

Hey, thanks for the report. Code 5 is usually a renderer process crash due to running out of memory. A few things that can help:

  1. Don’t keep long chats. If the chat has built up a lot of changed files, start a new one. This is the most common cause.

  2. Check if the project is in an iCloud folder (Desktop, Documents). If it is, move it to a local folder, like ~/dev.

  3. Try without extensions:

    cursor --disable-extensions
    

    If the crashes stop, turn extensions back on one by one to find the culprit.

  4. Disable GPU acceleration:

    cursor --disable-gpu
    
  5. Reset Cursor data (your backup will be kept):

    cd ~/Library/Application\ Support/
    mv Cursor CursorBackup
    

If none of that helps, please send:

  • Logs: Help > Open Logs Folder, the main.log file around the time of the crash
  • A screenshot from Cmd+Shift+P > Developer: Open Process Explorer right before the crash (check if renderer memory is growing above 3 to 4 GB)
  • Your list of installed extensions
  • Whether you’re using any MCP servers

Let me know how it goes.

1 Like

Hi, after the latest update, I am also encountering the same issue.

I am pretty sure this is related to the most recent update.

I’ve changed nothing on my Cursor recently that could cause this error, and it worked fine before the update.

Please, let me know if I can share some debug logs to help the dev-team.

Same here, after the latest update I made an hour ago or so. It worked fine as well before the update.

LE: For me it just crashes even if I don’t actively use it, all chat windows closed (after 1-2 minutes).

1 Like

Same here, keeps crashin every 2 minutes, cannot work anymore. After the latest update. Is there something we can do besides switching to Codex or CC?

Hi Dean,

for me it doesnt look like a OOM error:

This is the main log:
2026-03-04 09:41:42.355 [error] CodeWindow: renderer process gone (reason: crashed, code: 5)
2026-03-04 09:41:42.402 [info] Extension host with pid 48582 exited with code: 0, signal: unknown.
2026-03-04 09:41:42.402 [info] Extension host with pid 48581 exited with code: 0, signal: unknown.
2026-03-04 09:41:42.402 [info] Extension host with pid 48577 exited with code: 0, signal: unknown.
2026-03-04 09:42:23.774 [info] [CursorProclistService] Config enabled feature (subsample every 10s)
2026-03-04 09:47:24.682 [info] update#setState checking for updates
2026-03-04 09:47:25.973 [info] UpdateService onUpdateNotAvailable()
2026-03-04 09:47:25.973 [info] update#setState idle
2026-03-04 09:47:30.044 [error] CodeWindow: renderer process gone (reason: crashed, code: 5)
2026-03-04 09:47:30.120 [info] Extension host with pid 58070 exited with code: 0, signal: unknown.
2026-03-04 09:47:30.121 [info] Extension host with pid 58069 exited with code: 0, signal: unknown.
2026-03-04 09:47:30.122 [info] Extension host with pid 58064 exited with code: 0, signal: unknown.

None of your tips helped resolving this issue.

1 Like

Hey, I see a screenshot from Process Explorer showing a 2.8 GB peak across 18 processes, that really doesn’t look like a typical OOM. Thanks for the logs, they confirm the renderer is crashing repeatedly (09:41 and 09:47).

Since a few users in this thread report crashes right after updating to 2.6.11, this looks more like a regression in that version.

A few things that would help narrow it down:

  1. I see the CodeStream extension (294 MB, 10.5%) and three extension-host processes totaling about 1.1 GB. Can you share your full extension list? Also try running cursor --disable-extensions. If it stops crashing, it’s likely one of the extensions.

  2. Are you using MCP servers?

  3. If you haven’t already, try --disable-gpu. Exit code 5 is sometimes related to the GPU or the rendering process, not memory.

Let me know what you find.

Hi Dean,

  1. Here are the enabled extensions:


Running with –disable—extensions didn’t resolve my problem.

  1. Only Linear + Sentry, but both are not active after reinstalling Cursor (which didn’t solve it either).
  2. I did, didn’t help.

Thanks!

I think this is rendering problem of the tool responses. I see the problem on 2.5.x and 2.6.x version, not on.
I’m using Cursor on Ubuntu 24.04

Scenario:

  1. Do query like this: `XXX tool: ‘YYY’ - use this tool to get information how to … . Do several queries in parallel` with Composer
  2. In 70% after received tool responses (for 4-5 tool calls), the Cursor freeze. You need to wait 1-5min to become responsible and start working again.
  3. Next close Cursor with the chat visible and open it again. It will start with the last project with chat open and here it become unresponsive/freeze for couple of minutes. Then unfreeze
  4. Starting new Chat, again freeze Cursor.

At the end, the project cannot be use in Cursor anymore.

I’m using tool to query RAG and it returns JSON - list of documents in markdown with links, images, tables, etc, + sources ~8k tokens. I think such tool response kills Cursor especial when several tool calls is done in parallel.

Charts after I repoen Cursor - no active chats

main.log.txt (58.2 KB)

3 Likes

Confirming. After today update it is again tool which cannot be used. Crashing almost immediatly, but with each request…

Update to the Nightly version. I don’t have the bug on it, it seems to be fixed.

1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the middle of the developement, Cursor crach

Steps to Reproduce

I don’t know. I just try to continue development, but it happens again and again

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.6.11 (user setup)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Sonnet 4.6

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Title: Cursor crashes repeatedly on macOS - cursor-socket module missing, code 5

Environment:

  • OS: macOS Tahoe 26.3

  • Cursor version: latest as of 3.4.26

  • Crash error:

The window terminated unexpectedly (reason: 'crashed', code: '5')

Console errors:

Activating extension 'anysphere.cursor-socket' failed: Cannot find module
'/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket/out/main'

[transport] ConnectError: [unauthenticated] You must be a team member to access this resource

Troubleshooting already completed (none resolved the issue):

  • Updated Cursor via Cmd+Shift+P > “Cursor: Attempt Update”

  • Fully uninstalled, emptied Trash, and did a clean reinstall from Cursor · Download

  • Disabled majority of extensions, including github.vscode-pull-request-github and openai.chatgpt which had API proposal errors

  • Reduced project/codebase size

  • Checked macOS Privacy & Security settings

  • Issue started suddenly today with no changes made to the setup

Summary: The anysphere.cursor-socket core internal extension fails to activate on every launch after multiple clean installs. Cursor crashes within moments of opening. This appears to be a broken or missing file in the distributed build, not a user-side configuration issue.

That worked for me. Thanks!

Also getting a crash after the last update with multiple models after testing. Looks like complex tasks might be the issue here but can’t confirm. Causing additional credit usage after each crash.

im seeing the same issues of very laggy UI in the Cursor IDE and crashes after long usage in the same chat. already crashed 3 times today.

1 Like

Hi all, tried a lot of things.
Uninstalling and then installing the previous version 2.5.x works. Not the best fix for now but at least you can still use it and keep going :slight_smile:

1 Like

After today update still crashing.

Version: 2.7.0-pre.17.patch.0
VSCode Version: 1.105.1
Commit: 32a015bf4fbc26590f4b72cf1c6e4f0943cbc6f0
Date: 2026-03-04T11:41:36.069Z
Build Type: Stable
Release Track: Nightly
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Linux x64 6.17.0-14-generic

I still see a problem with freezing during the rendering of folded previews of tool responses, especially when they are called in parallel. I think the issue might be related to downloading or processing URI images from the markdown response or processing not-well formatted markdown. I didn’t notice this problem in version 2.4 with the simple preview.