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

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After the latest Cursor update, the IDE has become completely unusable. The app crashes repeatedly with the following error:

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

The crash happens every time I try to work. I cannot continue coding because Cursor closes instantly or within a few minutes of opening.

This is a critical issue — not a minor bug.

Steps to Reproduce

1.	Open Cursor (latest version)
2.	Start working on any project
3.	Within seconds or minutes, the window crashes
4.	Error dialog appears:

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

Expected Behavior

Cursor should remain stable and allow me to work without constant crashes.

Actual Behavior:

Cursor crashes repeatedly and becomes unusable. I am unable to do any development work.

Screenshots / Screen Recordings

Crashed code 5.png
Crashed code 5.png520×596 38.6 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.14 (Universal)
VSCode Version: 1.105.1
Commit: 1685afce45886aa5579025ac7e077fc3d4369c50
Date: 2025-12-11T01:12:35.790Z
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.6.0

Additional Information

This issue completely stops me from working. Please escalate this to the engineering team as a top-priority bug. Several users are experiencing similar crashes after recent updates.

Does this stop you from using Cursor

Yes - Cursor is unusable

2 Likes
2

Hey, thanks for the report. Let’s quickly narrow down the cause.

Please check:

  1. Extensions
  • Run from terminal: cursor --disable-extensions
  • If the crash stops, enable extensions one by one to find the culprit
  • Also open CMD+Shift+P > Developer: Open Process Explorer and send a screenshot right before the crash
  1. Network and proxy
  1. Clean environment
  • Open an empty folder without a devcontainer and MCP, then check if it reproduces

Data needed for engineering:

  • Help > Open Logs Folder > attach main.log
  • Any errors from Help > Toggle Developer Tools > Console
  • Confirm the results of cursor --disable-extensions and the test without a devcontainer
  • Whether you use a VPN/Zscaler or another proxy

We’re escalating this case. Please share the results of the steps above and attach logs so we can localize the issue faster.

3

it is same issue after the cursor --disable-extensions it crashing constantly

4

Thanks for the update. Since --disable-extensions didn’t help, this is most likely caused by corrupted workspace data.

Please try this workaround on macOS:

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

This will reset Cursor’s data while keeping a backup. After that, launch Cursor again.

This has helped other users with a similar issue: Cursor Crashing with error code 5 - Dec 14

This is a known issue, and the team is working on a fix.

Let me know if this helps.

5

I’m also experiencing this issue. I have reinstalled my Mac OS that’s how bad it is.

7

Flagging that I have this issue as well and that the fixes suggested above did not work for me unfortunately. Thanks for your efforts to fix this!

8

Hi there…Hello. I have the same problem, where after the last update, Cursor crashes with the above error practically every 15 minutes, making it completely unusable for continuous work. None of the above solutions work. Please treat this issue as a high priority. I would hate to have to abandon Cursor. Thank you.

1 Like
9

我也遇到这个问题，基本每次回答一次都会出现

10

Need help. I am also facing the same issue on Macbook M2 PRO, sequoia 15.5. It is working fine on Linux Ubuntu though. cursor is keep crashing sometime in 2-3 min after agent starts working which is making CPU usage around 50% on M2. I don’t think it should crash on 50-55% CPU usage proving enough RAM (7-8GB available). It started after an update I did last week which i think i was delaying since Dec 2025.

I am facing it even after the latest updates of Cursor. Will try to rename folder as suggested in one thread. Hope it won’t break any of my settings.

11

Same here starts after last update to 2.3.39, now we are on 2.3.40 ans still crash. Not a good reputation!
My research. Dev Tools say tons of errors but when the ■■■■■ begins ist logs that:

workbench.desktop.main.js:13688 [composer] Extension host became UNRESPONSIVE undefined

  1. {arch: ‘x64’, platform: ‘darwin’, channel: ‘stable’, client_version: ‘2.3.40’, extensionHostKind: ‘LocalProcess’, …}

workbench.desktop.main.js:55 ERR [Extension Host] (node:69662) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `Cursor Helper (Plugin) --trace-deprecation …` to show where the warning was created)

workbench.desktop.main.js:12674 [Extension Host] (node:69662) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `Cursor Helper (Plugin) --trace-deprecation …` to show where the warning was created)

2

workbench.desktop.main.js:13831 [Background Composer] Error updating branch on git status change: Error: No full commit provider registered
at Svs.getCurrentBranch (workbench.desktop.main.js:645:34504)
at pMt.value (workbench.desktop.main.js:13831:5937)
at Ce._deliver (workbench.desktop.main.js:49:2962)
at Ce._deliverQueue (workbench.desktop.main.js:49:3053)
at Ce.fire (workbench.desktop.main.js:49:3390)
at wnu.$gitStatusWasRun (workbench.desktop.main.js:12696:36169)
at JXe._doInvokeHandler (workbench.desktop.main.js:13633:23170)
at JXe._invokeHandler (workbench.desktop.main.js:13633:22912)
at JXe._receiveRequest (workbench.desktop.main.js:13633:21544)
at JXe._receiveOneMessage (workbench.desktop.main.js:13633:20361)
at pMt.value (workbench.desktop.main.js:13633:18388)
at Ce._deliver (workbench.desktop.main.js:49:2962)
at Ce.fire (workbench.desktop.main.js:49:3283)
at jyt.fire (workbench.desktop.main.js:12691:12156)
at MessagePort. (workbench.desktop.main.js:15681:18406)

workbench.desktop.main.js:13688 [transport] Connect error in unary AI connect ConnectError: [unauthenticated] You must be a team member to access this resource
at t (workbench.desktop.main.js:12706:476909)
at async Object.getTeamCommands (workbench.desktop.main.js:566:27065)
at async A9o.loadTeamCommands (workbench.desktop.main.js:15684:3633)

  1. {arch: ‘x64’, platform: ‘darwin’, channel: ‘stable’, client_version: ‘2.3.40’, error: {…}, …}

workbench.desktop.main.js:15684 Failed to load team commands: ConnectError: [unauthenticated] You must be a team member to access this resource
at t (workbench.desktop.main.js:12706:476909)
at async Object.getTeamCommands (workbench.desktop.main.js:566:27065)
at async A9o.loadTeamCommands (workbench.desktop.main.js:15684:3633)

No Extensions installed or activated.