Error code 536870904 from cursor IDE crash

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have the error message ‘536870904’ as shown in picture attached, several times a day.
It bcks my tasks and when I restart the app I can’t see last conversations or last tasks, even those completed. this forces me to as k for rebuild and recovery, which sometimes does not work, reintializing my thread messages with new title for chat.
All this increases token consumption

Steps to Reproduce

There is no specific step to reproduce it. It can appear during chat response generation/code written on files.
At the begining I thought it was due to multiple chat histories (since april there are multiple chats that some do no longer load without reason)
Secondly I thought it was disk/cpu or memory consumption but it seemed not the cause…

Operating System

Windows 10/11

Version Information

Version: 2.4.32 (system setup)
VSCode Version: 1.105.1
Commit: dac77182205e080f83e43f13ee42d822740a6e10
Date: 2026-02-09T05:01:38.814Z
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.26100

For AI issues: which model did you use?

I commonly use Auto for preventing token consumption with specific models

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report.

A likely cause in your version (2.4.32) is a memory leak in OpenTelemetry. To check:

  1. Ctrl+Shift+P → Developer: Toggle Developer Tools → Console tab
  2. Look for lines with [otel.error] or OTLPExporterError

If you see OTEL errors:

If there are no OTEL errors:

  • Ctrl+Shift+P → Developer: Open Process Explorer, then check which process is using the memory
  • Start new chats regularly instead of growing one long chat, this directly affects memory use
  • Try running cursor --disable-extensions to rule out extensions

Losing chat history is a side effect of an OOM crash that can corrupt the workspace state. Switching to new chats more often should reduce crashes and data loss.

Related thread with more context:

The team is aware of the issue. Let me know what you see in the console.

4

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.