Repeated renderer OOM crashes during agent-loop workflows

[Nils_Johannesson]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor 2.6.22 repeatedly crashes with renderer OOM during agent-loop workflows (reason: oom, code -536870904)

Steps to Reproduce

Repro Context (Observed Pattern)
Run sustained agent-driven operations (multi-step terminal/tool workflow).
Keep the session active through repeated agent-loop cycles.
Cursor eventually crashes with renderer OOM

Expected Behavior

Cursor should remain stable during long agent-loop tasks and handle large tool/output workloads without renderer termination.

Operating System

Windows 10/11

Version Information

Product / Version
Cursor 2.6.22
Environment
OS: Windows 11 (10.0.26100)
Workspace: C:\brain_rnd
Shell: PowerShell
Workflow type: long-running agent tasks with multiple tool calls / large output handling

For AI issues: which model did you use?

Premium

Additional Information

Cursor OOM Crash Report
Generated: 2026-04-02

Environment

• OS: Windows 11 (10.0.26100)
• Cursor: 2.6.22
• Workspace: C:\brain_rnd
• Crash signature: CodeWindow renderer process gone (reason: oom, code: -536870904)

Inspected files

1. C:\Users\NilorCool\AppData\Roaming\Cursor\logs\20260401T193930\main.log
2. C:\Users\NilorCool\AppData\Roaming\Cursor\logs\20260402T045241\main.log
3. C:\Users\NilorCool\AppData\Roaming\Cursor\logs\20260402T045241\window1\renderer.log
4. C:\Users\NilorCool\AppData\Roaming\Cursor\logs\20260402T045241\window2\renderer.log

Primary OOM events

• 2026-04-02 04:51:56.404
  [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
  Source: …\20260401T193930\main.log

• 2026-04-02 04:54:46.853
  [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
  Source: …\20260402T045241\main.log

• 2026-04-02 08:01:57.625
  [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
  Source: …\20260402T045241\main.log

• 2026-04-02 08:08:18.290
  [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
  Source: …\20260402T045241\main.log

What happens around the crashes

• Repeated agent-loop wakelock activity appears before each OOM:
  • [PowerMainService] Started wakelock … reason=“agent-loop”
  • [ComposerWakelockManager] Acquired wakelock … reason=“agent-loop”
• Immediately after OOM, extension hosts exit:
  • “Extension host with pid … exited with code: 0, signal: unknown.”

Additional signals found in renderer logs

• window1\renderer.log:
  • [warning] Failed to flush aggregating provider batch Canceled
  • [error] [MainThreadShellExec.execute] Session not found:
• window2\renderer.log:
  • Repeated [Extension Host] [otel.error] OTLPExporterError: Bad Request
    payload includes: {“error”:“Trace spans collection is not enabled for this user”}

Summary

• The crash pattern is consistent and renderer-specific OOM.
• Incidents correlate with active agent-loop sessions and repeated wakelock acquisition.
• OTEL 400 errors are frequent noise but not the direct crash signature.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor