Cursor keeps crashing (reason: 'oam', code: '-536870904')

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor keeps crashing seconds after opening after last update. The window terminated unexpectedly (reason: ‘oam’, code: ‘-536870904’)

Steps to Reproduce

Updated to the lastest version of cursor, everything started becoming laggy and then sudden error that only leaves cursor open for around 3 seconds.

Screenshots / Screen Recordings

image_2025-10-15_134005894.png
image_2025-10-15_134005894.png1509×1007 28.2 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.46 (user setup)
VSCode Version: 1.99.3
Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580
Date: 2025-10-14T01:21:46.830Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. Could you please try launching Cursor in safe mode to check if an extension is causing the crash? Run this in your terminal: cursor --disable-extensions

Let me know if safe mode helps or if the crash persists!

3

Hi all, I am facing the same issue. It started today. Cursor is constantly crashing, unusable. Tried running it without extensions as suggested and the issue persists. Please help us ASAP, this an essential tool for our business and it renders unusable.

4

Hey, could you let me know if this also happens in your other projects or in an empty Cursor window?

5

I tried closing all my chats and starting a new chat again, and it crashes. I tried not selecting “reopen” the windows after crash, but as soon as I start a chat, the program starts getting slow and crashes. I can do a call if you want to see the issue.

6

@deanrie I confirmed this is happening only in one project. A new project runs fine.

7

Facing the same issue on 1.7.46. crashes 10-20 seconds after opening up a project (having done nothing). Doesn’t crash on other projects, so maybe related to chat/agent history? This is urgent and is blocking our work, please fix quick. Opening in safe mode seems to work though

8

Hey all, thanks for the reports. This matches an ongoing investigation into crashes in versions 1.7.44–1.7.46, especially in projects with chat history.

Immediate workaround:

Since this is project-specific, try clearing the workspace storage for the affected project:

  1. Close Cursor completely
  2. Go to:
    • Windows: %APPDATA%\Cursor\User\workspaceStorage
    • macOS: ~/Library/Application Support/Cursor/User/workspaceStorage
    • Linux: ~/.config/Cursor/User/workspaceStorage
  3. Find the folder matching your project
  4. Delete that folder
  5. Reopen your project

This will clear chat history for that project but should make Cursor usable again.

@goamaan since safe mode works for you, the issue might be extension-related. Please try disabling extensions one by one to find the culprit.

@daspuru @DirkJ could you confirm if you have any MCP servers configured?

The team is actively investigating this. I’ll escalate this thread for visibility.

9

Yes I had Attlasian and Context7 MCPs, I “fixed“ the issue by updating to the nightly version for now. I was on default

10

Some users reported MCP Atlassian crashes in Cursor. Glad to hear the nightly build fixed your issue.

11

@deanrie Nothing you suggested fixed anything. I also disabled the only MCP i had (Framelink FIgma MCP) and uninstalled over 80 extensions but nothing helped (i’m fairly sure it’s not the extensions). What else can I do?

12

Thanks for the extra info. Yeah, that’s pretty odd. Please try reinstalling Cursor completely.

Do the following:

  1. Fully quit Cursor
  2. In your file explorer, open:
Windows: %APPDATA%\Cursor
macOS: ~/Library/Application Support/Cursor
Linux: ~/.config/Cursor/User

and rename the folder to Cursor.old (this is a backup)

  1. Restart Cursor (it will create a fresh folder)

Hope this helps.

13

Did what you suggested (renamed folder, cursor did a “fresh” install, didnt import anything from vscode) and opened the same project, and still have the same issue. At this point I’m not sure what it could be. Also fully uninstalled the app but no luck. Switched back to a much older version (1.5.x) and still seeing this issue?

14

It’s really strange that even older versions behave the same. Since you did a clean install and the issue persists across versions, it might be system‑level or project‑specific.

Please try creating a completely empty project and see if Cursor still crashes. Just make a new folder anywhere and open it in Cursor.

Also check for any system‑level Node.js processes or other dev tools that might interfere. The error code you mentioned -536870904 is quite specific, so this may need deeper investigation.

If the empty project works fine but your main project crashes, something in your project files is likely causing the issue.

Try opening the Process Explorer before Cursor crashes to watch resource usage. Also open the logs folder and share the latest logs: open the command palette → “Open Logs Folder,” then share the most recent log files.

15

Error happened again

Opened the logs and asked agent a task that requiered mcp. (Attlasian)

If the agent window with the tab that did mcp call is open, it crashes again on Reopen.
If I delete the tab quickly after reopen and relaunch cursor, it seems to be fine.

This is what showed up in the logs

025-10-17 10:38:45.687 [info] updateURL ``https://api2.cursor.sh/updates/api/update/win32-x64-user/cursor/1.7.46/17d7fa25a1e3718976eb7293b360307c5a1a3698ffa148c0ca43c859d8c5de57/stable
2025-10-17 10:38:45.688 [info] update#setState idle
2025-10-17 10:38:46.980 [warning] [Tray] Using fallback Windows icon: C:\Users\Remy\AppData\Local\Programs\cursor\resources\app\resources\win32\code.ico. Consider adding tray-specific icons.
2025-10-17 10:39:15.699 [info] update#setState checking for updates
2025-10-17 10:39:15.832 [info] update#setState idle
2025-10-17 10:54:39.123 [warning] [Tray] Using fallback Windows icon: C:\Users\Remy\AppData\Local\Programs\cursor\resources\app\resources\win32\code.ico. Consider adding tray-specific icons.
2025-10-17 10:58:17.060 [warning] [Tray] Using fallback Windows icon: C:\Users\Remy\AppData\Local\Programs\cursor\resources\app\resources\win32\code.ico. Consider adding tray-specific icons.
2025-10-17 11:24:42.686 [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
2025-10-17 11:24:42.756 [info] Extension host with pid 17356 exited with code: 0, signal: unknown.
2025-10-17 11:27:57.828 [warning] [Tray] Using fallback Windows icon: C:\Users\Remy\AppData\Local\Programs\cursor\resources\app\resources\win32\code.ico. Consider adding tray-specific icons.
2025-10-17 11:27:59.058 [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
2025-10-17 11:27:59.086 [info] Extension host with pid 24872 exited with code: 0, signal: unknown.
2025-10-17 11:28:03.356 [warning] [Tray] Using fallback Windows icon: C:\Users\Remy\AppData\Local\Programs\cursor\resources\app\resources\win32\code.ico. Consider adding tray-specific icons.

16

Facing same issue as others have mentioned. Cursor keeps crashing a few minutes after launch with this line in the logs:

[error] CodeWindow: renderer process gone (reason: oom, code: -536870904)

I went through some troubleshooting, but nothing worked.

:magnifying_glass_tilted_left: Observations

  • Crash only happens when I open a specific project folder (~600 MB). When I open other projects (relatively smaller ones ~100 MB), Cursor does not crash.

  • Always tied to an OOM (out of memory) event in the renderer process, not the Node side.

  • Main process stays alive, and the extension host exits cleanly (code: 0), but the renderer (UI) dies.

  • My logs also showed this earlier:

    • [storage main] detected slow close() operation: Time: 3322ms, DB size: 2889445376b, Large Keys: aiCodeTrackingLines:2033313

:test_tube: Steps Tried

  1. Cleared all Cursor local data
    Deleted these folders:
  • C:\Users\\AppData\Roaming\Cursor\User\globalStorage
  • C:\Users\\AppData\Roaming\Cursor\Service Worker

Cursor recreated them on launch, but it still crashed with the same OOM code.

  1. Disabled GPU rendering
    Tried launching with:
  • --disable-gpu
  • --disable-software-rasterizer
  • --in-process-gpu
  • --disable-gpu-compositing

No change, still crashes.

  1. Disabled extensions and AI panels
    Tried --disable-extensions and closing all AI windows before exit (when it stayed open long enough). Didn’t help.

  2. Increased memory allocation

Tried launching with:

--max-old-space-size=12288

  1. Reverted back to my original storage folders
    Since the clean rebuild didn’t fix anything, I reverted to my old data.

:puzzle_piece: System Details

  • Windows 11

  • Cursor v1.7.54

  • 32 GB RAM

:puzzle_piece: Cursor Details

  • Version: 1.7.54 (user setup)

  • VSCode Version: 1.99.3

  • Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0

  • Date: 2025-10-21T19:07:38.476Z

  • Electron: 34.5.8

  • Chromium: 132.0.6834.210

  • Node.js: 20.19.1

  • V8: 13.2.152.41-electron.0

  • OS: Windows_NT x64 10.0.26200

17

столкнулся с той же проблемой сегодня, как работать не понимаю, терчть чаь вообще не вариант, я его даже не могу экспортировать, просто не успеваю, так бы я в новом чате дал бы экспорт старого для анализа и понимания, в итоге ничего, компенсирует ли курсор это своим пользователям, так как запросы то уходят и денежко то тратятся исходя из новой политики ценообразования, а в итоге они просто сгорают !?