Cursor crashes on every prompt — unusable despite Pro+ subscription

Support Bug Reports
1

Describe the Bug

I’m extremely frustrated at this point.

Cursor crashes on every single prompt. The app is effectively unusable. I cannot get any work done.

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

I’m paying for a Pro+ subscription and getting a completely broken product in return. This is not a minor bug - it’s a total blocker.

Please treat this as a critical stability issue. Screenshot attached.

Steps to Reproduce

Steps to reproduce? Just send a prompt…

Expected Behavior

That it works and not crashes?

Operating System

MacOS

Version Information

Version: 2.6.12 (Universal)
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z (1 day ago)
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?

5,3 Codex

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, this is a known issue that’s gotten worse with the recent 2.6.x releases. Several users are reporting the same code: 5 renderer crash, and there’s a bigger thread tracking it here: Cursor keeps crashing - 2.6.11

A few things to try:

  1. Start fresh chats: long chat histories are the most common trigger. Close all open chats, fully quit Cursor (Cmd+Q), then reopen.

  2. Disable extensions:

    cursor --disable-extensions

  3. Disable GPU acceleration:

    cursor --disable-gpu

  4. Make sure the project isn’t in an iCloud-synced folder (Desktop, Documents). If it is, move it to something like ~/dev.

  5. Reset Cursor state (your settings are backed up):

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

If none of that helps, I’d need:

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

As a last resort, some users have had success downgrading to 2.5.x until this is resolved.

The team is aware of the increased crash reports with 2.6.x. Let me know what you find.

5

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