Cursor 1.7.4x crashes when GPU is enabled (renderer code 5)

RSI_PLC · October 10, 2025, 7:41pm

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

During a long-running AI chat operation the window crashes (renderer). Initially happened while retrieving PR logs via GitHub MCP, but I can reproduce even with MCP disabled. Disabling GPU/hardware acceleration prevents the crash entirely.

Steps to Reproduce

Launch Cursor normally (GPU enabled).
Start an AI chat that streams for a while (e.g., log retrieval).
After some time (seconds to a few minutes), the window closes and the crash dialog appears:
“The window terminated unexpectedly (reason: ‘crashed’, code: ‘5’)”.

Expected Behavior

Chat should complete and the window should remain stable with GPU enabled.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.44 (Universal)
VSCode Version: 1.99.3
Commit: 9d178a4■■■89981b62546448bb32920a8219a5d0
Date: 2025-10-10T15:43:37.500Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

GPT-5 Thinking

Additional Information

I can reproduce without GitHub MCP enabled.
Clearing caches (GPUCache, Code Cache) did not help.

Main/logs near crash:
2025-10-10 21:06:52.960 [error] CodeWindow: renderer process gone (reason: crashed, code: 5)
2025-10-10 21:06:53.240 [info] Extension host with pid 57847 exited with code: 0, signal: unknown

Workaround that works:

Launch with GPU disabled (–disable-gpu).

Does this stop you from using Cursor

Yes - Cursor is unusable

nicholastenbrink · October 10, 2025, 9:23pm

I am seeing the same Error.
I was using claude-4.5-sonnet

Version: 1.7.44 (Universal)
VSCode Version: 1.99.3
Commit: 9d178a4■■■89981b62546448bb32920a8219a5d0
Date: 2025-10-10T15:43:37.500Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

deanrie · October 11, 2025, 11:25am

Hey, thanks for the report. It looks like this matches an ongoing investigation. Several users are seeing the same renderer crash (code 5) during long AI operations, especially when summarizing chat.

Please answer a few questions:

Can you confirm this happens specifically during chat summarization?
Does this also happen in your other projects?
And could you share the list of your MCP servers?

Similar thread we’re already investigating:

Your workaround with --disable-gpu is the best option for now until the team fixes this.

RSI_PLC · October 11, 2025, 11:52am

Can you confirm this happens specifically during chat summarization?

Hard to say in which part it happens. A few engineers in my team are experiencing it immediately after startup, without engaging with the chat itself. These engineers had previously executed long agent tasks that required context compression, as they were collecting a lot of data from PRs and then instructing the agent to produce a summary. Could it be that Cursor is struggling when loading conversations with long conversation history, or conversation that needed summarisation ?

Does this also happen in your other projects?

Haven’t faced it yet on other projects yet, mainly as I only used the concerning Cursor version range for one day, and only within the given project. I’d need more time to confirm.

And could you share the list of your MCP servers?

github-mcp
atlassian-mcp

deanrie · October 11, 2025, 12:08pm

Thanks for the info. This detail about startup crashes when loading conversations with a long history is very helpful.

Several users also mentioned the issue might be related to atlassian-mcp.

We’re actively investigating this with the team. The pattern you described (crashes when loading conversations that previously needed summarization) matches what we’re seeing across multiple reports.

It’d be great if you could share more info after further testing.

Chris_Conner · October 13, 2025, 1:57pm

I’m also seeing this same issue. I’m running on Mac M2 and I have the github-mcp. I tried using –disable-gpu and that doesn’t seem to do anything. Is there anything else I can try?

deanrie · October 13, 2025, 2:02pm

What’s your macOS version? Also try launching in safe mode with this command: cursor --disable-extensions. Please check what Process Explorer shows as well.

nicholastenbrink · October 13, 2025, 3:05pm

Can confirm that it is occurring during the “Summarizing Chat context”
while I am using a Prompt that is using the Atlassian-MCP Server (latest version)

deanrie · October 13, 2025, 4:10pm

Hey, thanks for the info, that’s very helpful.

RSI_PLC · October 15, 2025, 7:59am

Sharing more info about the crash

/Applications/Cursor.app/Contents/MacOS/Cursor --disable-gpu
[main 2025-10-15T07:53:03.775Z] updateURL https://api2.cursor.sh/updates/api/update/darwin-universal/cursor/1.7.46/3994ad613e01a2a418d40eae8e5f2026505fb6774777d40ae861ddb30ee42fa1/stable
[main 2025-10-15T07:53:03.778Z] update#setState idle
[main 2025-10-15T07:53:04.999Z] [Tray] getMacOSIconPath: hasNotifications: false
[main 2025-10-15T07:53:33.780Z] update#setState checking for updates
[main 2025-10-15T07:53:34.416Z] UpdateService onUpdateNotAvailable()
[main 2025-10-15T07:53:34.416Z] update#setState idle
[main 2025-10-15T07:53:53.934Z] Extension host with pid 83523 exited with code: 0, signal: unknown.
[main 2025-10-15T07:54:07.716Z] CodeWindow: renderer process gone (reason: crashed, code: 5)
[main 2025-10-15T07:54:08.011Z] Extension host with pid 87590 exited with code: 0, signal: unknown.
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
  at s.send (node:electron/js2c/browser_init:2:93094)
  at _.send (node:electron/js2c/browser_init:2:76130)
  at eb.send (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:35:28474)
  at om.sendBuffer (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13410)
  at om.send (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13350)
  at om.sendResponse (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13201)
  at dc.value (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:34:343)
  at C._deliver (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:2937)
  at C._deliverQueue (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:3028)
  at C.fire (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:3364)
  at dc.value (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:45:14703)
  at C._deliver (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:2937)
  at C.fire (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:3257)
  at ForkUtilityProcess.V (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:30:8080)
  at ForkUtilityProcess.emit (node:events:524:28)
  at ForkUtilityProcess.a.emit (node:electron/js2c/browser_init:2:71934)
  at UtilityProcessWrapper.callbackTrampoline (node:internal/async_hooks:130:17)
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
  at s.send (node:electron/js2c/browser_init:2:93094)
  at _.send (node:electron/js2c/browser_init:2:76130)
  at eb.send (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:35:28474)
  at om.sendBuffer (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13410)
  at om.send (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13350)
  at om.sendResponse (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13201)
  at r.then.Error.sendResponse.id (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:14290)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
  at s.send (node:electron/js2c/browser_init:2:93094)
  at _.send (node:electron/js2c/browser_init:2:76130)
  at eb.send (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:35:28474)
  at om.sendBuffer (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13410)
  at om.send (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13350)
  at om.sendResponse (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13201)
  at dc.value (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:34:343)
  at C._deliver (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:2937)
  at C.fire (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:3257)
  at file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:30:7261
  at dc.value (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:30:5906)
  at C._deliver (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:2937)
  at C._deliverQueue (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:3028)
  at C.fire (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:3364)
  at dc.value (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:30:5765)
  at C._deliver (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:2937)
  at C.fire (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:32:3257)
  at App.V (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:30:8080)
  at App.emit (node:events:536:35)
  at BrowserWindow.<anonymous> (node:electron/js2c/browser_init:2:12666)
  at BrowserWindow.emit (node:events:524:28)
  at BrowserWindow.callbackTrampoline (node:internal/async_hooks:130:17)
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
  at s.send (node:electron/js2c/browser_init:2:93094)
  at _.send (node:electron/js2c/browser_init:2:76130)
  at eb.send (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:35:28474)
  at om.sendBuffer (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13410)
  at om.send (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13350)
  at om.sendResponse (file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:33:13201)
  at file:///Applications/Cursor.app/Contents/Resources/app/out/main.js:34:28
  at runNextTicks (node:internal/process/task_queues:60:5)
  at listOnTimeout (node:internal/timers:545:9)
  at process.processTimers (node:internal/timers:519:7)

nicholastenbrink · October 24, 2025, 3:16pm

I have also attempted to disable GPU and it did not net positive results.
It even appeared to cause the crashes to occur sooner than later.

Topic		Replies	Views
Error reason: 'crashed', code: '5' Bug Reports	5	52	November 2, 2025
Cursor's chat freezes every so often Bug Reports	3	1306	March 14, 2025
Cursor 1.4.4 keeps Crashing Bug Reports	4	91	September 5, 2025
The window terminated unexpectedly (reason: 'oom', code: '-536870904') Bug Reports	58	5181	March 31, 2025
Cursor crashes very frequently since the updating several days ago Bug Reports	13	822	April 24, 2025