[Linux] IDE crashes with clean-exit during Agent loop after 3.19.7

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After updating to Cursor 3.19.7 on Linux, the IDE window repeatedly terminates with:

The window terminated unexpectedly
reason: ‘clean exit’

main.log shows:
CodeWindow: renderer process gone (reason: clean-exit, code: )

Earlier the same day there were also native crashes:
CodeWindow: renderer process gone (reason: crashed, code: 135)
(135 = 128+7 → SIGBUS)

This only affects the Cursor IDE Electron window. Cloud/Background Agents continue to work normally. Crashes frequently occur during or shortly after local Agent loops (agent-loop / agent-loop-resumed). Compacted agent state DB (state.vscdb ~4.7GB → ~466MB) and reduced swap usage did NOT stop the clean-exit crashes.

Steps to Reproduce

  1. Use Cursor IDE 3.19.7 on Ubuntu 24.04 (Linux x64).
  2. Open a normal workspace and start a local Agent chat in the IDE.
  3. Let the agent run (tool calls / edits / longer session). Sometimes also happens with multiple agents (activeCount ≥ 2).
  4. Within minutes (sometimes mid-run, sometimes shortly after), the IDE window dies with “clean exit”.
  5. Reopen Cursor — Agents (cloud) still work; IDE crashes again when using Agent in the IDE.

Notes:

  • Happened 0 times on previous day logs before this update.
  • Still reproduces after GC Agent KV Blobs, Delete Old Chats, and swapping a compacted state.vscdb.
  • Not fixed by lowering swap usage.

Expected Behavior

The IDE window should stay open while Agent runs. Renderer / extension host should not exit. Cloud Agents and IDE Agent should both be stable; IDE should not crash with clean-exit / SIGBUS during agent-loop.

Operating System

Linux

Version Information

IDE:
Version: 3.19.7
VSCode Version: 1.128.0
Commit: 90de2327392570a5f5f625c656c6749d228e6430
Electron: 42.10.0
Date: 2026-09-02T23:03:07.739Z

For AI issues: which model did you use?

Multiple / Auto (default). Also reproduced earlier with grok-4.6 in agent-loop sessions. Crash appears tied to IDE Agent UI/renderer, not a single model.

For AI issues: add Request ID with privacy disabled

feabc909-897f-4056-bf7f-68e0652ee260

Additional Information

  • Machine: Ubuntu 24.04.4 LTS, x64, Intel UHD Graphics 730 (not AMD), ~15 GiB RAM
  • Pattern: crashes cluster around PowerMainService agent-loop / agent-loop-resumed
  • Often: Extension host exits (code 0) → immediately renderer clean-exit
  • Morning: mix of clean-exit and crashed code 135 (SIGBUS) + Crashpad
  • Afternoon after state compaction: mostly clean-exit only; still reproducible (e.g. 17:33:50)
  • IDE-only: Cloud/Background Agents do not crash
  • Ruled out as root cause: GPU driver reset, kernel OOM killer, third-party extension as primary trigger, oversized state.vscdb alone, high swap alone
  • Mitigations tried: Delete Old Chats, GC Agent KV Blobs, compacted state.vscdb (~466MB), reduced MCP overlap — startup freeze improved, crashes remain
  • Workaround: use Agents (cloud) for heavy work; avoid long/multi agent-loop inside IDE window

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report. The logs and version info help a lot.

This is a known issue we’re tracking. It’s specific to Linux on 3.19.x. A runtime change in 3.19 can cause the IDE window or the extension host to quit with a clean exit, sometimes SIGBUS or code 135, and it shows up more often during heavier work like agent sessions. It’s not related to your state DB size or swap, so there’s no point tuning those further. Windows and macOS aren’t affected. Nightly and Stable are currently the same 3.19.7 build, so switching channels won’t help.

For now, the best workaround is to roll back to 3.18.25:

  • Fully quit Cursor and make sure no Cursor processes are still running.
  • Install 3.18.25 from Cursor · Download older versions are available on the page.
  • If you use the .deb package, run sudo apt-mark hold cursor so it won’t update back to 3.19.7. After the patched release ships, run sudo apt-mark unhold cursor.

I can’t share an exact ETA yet, but I’ll post in the thread when there’s an update. If crashes still happen after rolling back to 3.18.25, let me know here.