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

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After update to version 2.0.64 (before it was <2) I constantly getting this error.
Never saw this error before.
The app crushes in 100% cases.
Yesterday I had the same issue, but reboot of the system helped. Today it doesn’t help.

I am using devcontainers for my projects. On Reopen of Devcontainer I am getting this error. All projects are old (~1 year).

I have Atlassian MCP as mentioned in this topic (The window terminated unexpectedly (reason: ‘crashed’, code: ‘5’) - 100% reproducible with Atlassian MCP).

What I’ve tried:

  • turn off MCPs
  • deleting and reinstalling docker containers
  • cleared chats

Added screenshot with Process Explorer and DevTools console.

Help please.

Steps to Reproduce

in my case just open Cursor

Expected Behavior

It works with devcontainers

Screenshots / Screen Recordings

image (3).jpg
image (3).jpg1920×1362 434 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.64
VSCode Version: 1.99.3
Commit: 25412918da7e74b2686b25d62da1f01cfcd27680
Date: 2025-11-06T04:35:14.424Z (1 day ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.3.0

For AI issues: which model did you use?

Sonnet 4 and other Claude models

Does this stop you from using Cursor

Yes - Cursor is unusable

Cursor Crashes Constantly After Latest Update (code: ‘5’) — Cannot Work at All
Cursor crashing with error code 5
3

Hey, thanks for the report - this matches a known issue we’re already working on.

Please try a few checks:

  • Run: cursor --disable-extensions from a terminal - does it still crash?
  • Open a simple project without a devcontainer - same issue?
  • Fully remove Atlassian MCP from Settings (not just disable)
  • If possible, share clearer errors from DevTools Console

The team is on it; we just need to narrow down what’s triggering the crash in your case.

4

Hey seems like we solved the issue. The reason was the Zscaler program, which our company forced to install.

Zscaler handles Cursor traffic in some weird way and api.cursor.sh were timing out. We solved it on Zscaler side.

5

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