Latest version of cursor app crashes regularly on mac sonoma 14.8.3

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Random app crashes since the latest version of cursor app loaded every few minutes when agent is thinking or generating code

Steps to Reproduce

Can’t isolate the crash any further than appears to happen randomly every few minutes when agent is thinking or generating code

Expected Behavior

It’s didn’t crash before

Operating System

MacOS

Version Information

Version: 2.5.20
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z (1 day ago)
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 23.6.0

For AI issues: which model did you use?

Sonnet 4.6 and Composer 1.5

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, thanks for the report. Crashes during agent generation on macOS arm64 have come up before, so let’s dig into what’s happening in your case.

A few things to try and check:

  1. Run without extensions. Launch from Terminal: cursor --disable-extensions. If the crashes stop, re-enable extensions one by one to find the one causing it.

  2. Check resource usage. Right before the crash, open Cmd+Shift+P then run Developer: Open Process Explorer and take a screenshot. This helps confirm if it’s an out-of-memory issue.

  3. Logs. After the crash, go to Help > Open Logs Folder and grab main.log. Also check Help > Toggle Developer Tools > Console for any errors.

  4. Test in a clean workspace. Open an empty folder with no project and no MCP, then try using the agent there. Does it still crash?

  5. Reset workspace data if nothing else helps:

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

    Then restart Cursor. This resets cached data while keeping a backup.

Also, do you see a specific error code when it crashes, like code: '5'? And are you using a VPN or proxy?

The team is aware of crash issues on macOS. Your logs and the info above will help narrow down the cause.

4

Hey Dean… Ok I do get a code 5 each time. Attached is the screenshot from the dev tools console. I couldn’t find P{en Logs Folder i the help menu ? I’ll try the rest of your suggestions when I have a moment. Thanks

Image 21-02-2026 at 16.26
Image 21-02-2026 at 16.261110×976 169 KB

1 Like
5

Thanks for the info. Switch to the Console tab (top, next to Elements) and check if there are any errors with [otel.error] or OTLPExporterError. That’ll help us understand what’s happening right before the crash.

About the logs: “Open Logs Folder” should be in the command palette Cmd + Shift + P. You can also open it via Finder:

~/Library/Application Support/Cursor/logs/

Inside, there will be a folder with the date. We need the main.log file from there.

One more thing: exit code 5 on macOS is often related to an OOM (out of memory) crash of the renderer process. A common trigger is long agent chats. Please try:

  • Close all old chats and start a new chat more often, don’t keep one endless chat
  • Before it crashes, open Process Explorer (Cmd+Shift+P → Developer: Open Process Explorer). If the renderer is using more than 3 to 4 GB, that confirms an OOM issue

If nothing from my previous message or this one helps, send main.log and a screenshot of the Console tab, and we’ll dig in further.

6

Thanks Dean. You’re right - I’d slipped into the bad habit of letting the chat re-contextualise too much. I’ve gone back to shorter chats with summaries and haven’t had a crash since, using Composer 1.5 at leasr