Hey thanks for the report. The error “renderer process gone (reason: oom, code: -536870904)” means the Cursor renderer process exceeded ~4GB of memory and was terminated by Windows - this is a problem with large chat histories on Windows.
Similar reports:
- Cursor crashes frequently on Windows: renderer process exceeds 4GB memory (possible memory leak?)
- The windows terminated unexpectedly (reason: 'oom',code:'-536870904')
For now, try these steps:
- Start a new chat instead of continuing the current one (~25k lines is a lot of context)
- Export your profile
- Delete the corrupted state.vscdb: go to
%APPDATA%\Cursor\User\globalStorage, find the folder with state.vscdb.corrupted.* (~14.8GB!) and delete all state.vscdb* files in that folder - If you’re on version 2.3.35-2.3.41, check your logs for OTEL errors (OpenTelemetry memory leak). If you find them, downgrade to 2.3.34 and turn off auto-updates in Settings > Application > Update > “none”
- Use
Ctrl+Shift+P> Developer: Open Process Explorer to monitor the renderer process memory usage in real time
Technical reason: Electron on Windows has a ~4GB limit for renderer processes (32-bit pointer compression), and large chat histories plus AI workflows accumulate memory without releasing it. state.vscdb corruption happens when a crash occurs during a write operation.
I’ll pass this to the team for investigation.