Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
The editor window dies and shows: The window terminated unexpectedly (reason: ‘clean-exit’, code: ‘0’). This is not OOM and not a crash code. main.log records CodeWindow: renderer process gone (reason: clean-exit, code: ). It happens several times in a day, often around Agent activity (PowerMainService wakelock reason=agent-loop) and sometimes after RendererPing reports the window blocked (~15–20s). Extension hosts then exit with code 0.
Steps to Reproduce
Use Cursor 3.19.7 on Linux Mint 22.3.
Work in a workspace with Agent running.
After some time (or after the window is blocked), the renderer exits cleanly and the unexpected-termination dialog appears.
Reopen restores the window; the same clean-exit happens again later.
Reproduced many times on 2026-09-04, including: 10:40:11, 10:40:49, 10:44:44, 12:10:51, 12:12:53, 13:10:37, 13:11:06, 13:12:24, 13:15:30.
Expected Behavior
The window should stay open. If the renderer dies, it should report a real crash or OOM reason, not a clean-exit treated as unexpected termination.
Screenshots / Screen Recordings
Operating System
Linux
Version Information
Version: 3.19.7
VSCode Version: 1.128.0
Commit: 90de2327392570a5f5f625c656c6749d228e6430
Date: 2026-09-02T23:03:07.739Z
OS: Linux x64 7.0.0-31-generic
For AI issues: which model did you use?
IDE window crash, not a model-quality issue
Additional Information
2026-09-04 13:11:06.824 [error] CodeWindow: renderer process gone (reason: clean-exit, code: )
2026-09-04 13:12:24.558 [error] CodeWindow: renderer process gone (reason: clean-exit, code: )
2026-09-04 13:15:30.133 [error] CodeWindow: renderer process gone (reason: clean-exit, code: )
2026-09-04 13:15:48.979 [warning] [RendererPing] window 4 (pid 0) blocked for ~20000ms
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor