Cursor crashes with "reason: 'oom'" when using Composer on Windows 11 RTX system

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor crashes repeatedly when using Composer to generate or edit code.

The crash message is:
“The window terminated unexpectedly (reason: ‘oom’, code: -536870904)”

This happens consistently while working on my project (LagOff), especially during Composer actions.

System info:
Cursor version: 2.4.37 and also tested 2.5.16 Early Access
OS: Windows 11 (build 26200)
GPU: NVIDIA RTX
Network adapter: Killer E2600 Ethernet Controller
Electron: 39.x

Troubleshooting already attempted:

  • Reinstalled Cursor completely
  • Switched between Stable and Early Access
  • Disabled GPU acceleration
  • Disabled Killer xTend services
  • Increased virtual memory
  • Disabled extensions
  • Tested fresh Cursor profile

The crash still occurs.

The log shows:
CodeWindow: renderer process gone (reason: oom, code: -536870904)

This appears to be the known renderer OOM issue discussed on the Cursor forum.

Steps to Reproduce

  1. Open Cursor on Windows 11
  2. Open a project folder (LagOff project in my case)
  3. Open Composer
  4. Ask Composer to generate or edit code
  5. Wait for Composer to start generating
  6. After some time (sometimes immediately, sometimes after a few actions), Cursor crashes

Crash message:
“The window terminated unexpectedly (reason: ‘oom’, code: -536870904)”

This happens consistently when using Composer.

Expected Behavior

Cursor should generate code without crashing.

Screenshots / Screen Recordings

Screenshot 2026-02-13 174115.png
Screenshot 2026-02-13 174115.png550×169 6.07 KB

Operating System

Windows 10/11

Version Information

Version: 2.4.37 (user setup)
VSCode Version: 1.105.1
Commit: 7b9c34466f5c119e93c3e654bb80fe9306b6cc70
Date: 2026-02-12T23:15:35.107Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer

For AI issues: add Request ID with privacy disabled

f9a7046a-279b-47e5-ab48-6e8dc12daba1

Additional Information

Cursor crashes with renderer OOM error when using Composer.

Error message:
“The window terminated unexpectedly (reason: ‘oom’, code: -536870904)”

This happens consistently when generating or editing code in Composer.

Already tried reinstalling Cursor, switching release tracks, disabling extensions, and using Early Access builds.

Request ID attached for debugging.

Does this stop you from using Cursor

Yes - Cursor is unusable

3

also here is the crash logs

output.zip (8.0 KB)

4

Hey, thanks for the report. The Renderer process in Cursor (Electron/Chromium) hits a hard hardware limit of about 4 GB of memory, then crashes with this OOM code. This does not depend on the total amount of RAM in your system.

I can see you have already tried a lot (reinstall, GPU acceleration, extensions, Early Access). Here is what else is worth checking:

  1. OTEL memory leak check:
    Ctrl+Shift+P > Developer: Toggle Developer Tools > Console. Look for lines with [otel.error] or OTLPExporterError. If you see them, that is an additional memory leak on top of the main limit.

  2. Workarounds that actually help:

  • Rotate chats. Start a new chat when the current one gets big, especially before long agent workflows.
  • Monitor memory: Ctrl+Shift+P > Developer: Open Process Explorer.
  • If it is already crashing on startup, delete recent chats via Chat History.

More discussion and context here: Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans

Let me know if you see any OTEL errors in the Console, and if rotating chats helps.