Cursor 3.19.x on Linux: `The window terminated unexpectedly (reason: 'clean-exit', code: '0')` and high RAM use after updating (fixed in 3.19.13)

Context

Source(s): https://forum.cursor.com/t/regression-in-3-19-7-on-ubuntu-high-ram-usage-and-renderer-exits-fixed-by-downgrading-to-3-18-25/170546 Signal: 427 views, 15 posts; reports from Ubuntu 26.04, Linux Mint 22.x and KDE Neon (Wayland); several said Cursor was unusable. Status: reported working by source, not reproduced by us.

Problem

After updating Cursor from 3.18.25 to 3.19.7 on Linux (APT repository and others), Cursor uses much more RAM and the window closes on its own with the dialog above, sometimes right at launch, sometimes after a while with an agent running. Choosing "New Window" in the dialog can loop back into the same error. System logs show no OOM kill.

Error (redacted / normalized)

The window terminated unexpectedly (reason: 'clean-exit', code: '0')

CodeWindow: renderer process gone (reason: clean-exit, code: <unknown>)

Applies when

Linux x64 (Ubuntu 26.04, Linux Mint 22.1/22.3, KDE Neon 24 on Wayland), Cursor 3.19.7 (Electron 42.10.0), stable and nightly tracks.

Confirm it is this problem

1. Help > About shows a 3.19.x version below 3.19.13. → expect: 3.19.7 in every report in the thread.
2. main.log contains CodeWindow: renderer process gone (reason: clean-exit, code: <unknown>) (reported by a commenter).

Not this when / boundary

Memory growing to 10–15 GB on Windows; staff said that is likely a different issue and asked for a new thread. Near-overlap: fix/84 covers the same dialog text in VS Code 1.129.0 on Linux, which is a different product and version.

Root cause

Staff said it is specific to Linux on 3.19.x: a change in the Electron runtime shipped in 3.19 can make the window process exit cleanly (the "clean-exit, code 0" message) and use more memory than before. Staff said Windows and macOS should not be affected.

Fix

1. Update Cursor to 3.19.13 or later. → expect: staff said a fix "should have rolled out" with 3.19.13, and a commenter on Linux Mint replied "I updated it and it is working fine."
2. If you can't update yet, go back to 3.18.25 from the official download page and pause updates until the fix is installed (staff workaround). → expect: the original poster confirmed memory use returned to normal and the window no longer closes on 3.18.25.

How to verify

Cursor stays open through a normal session with an agent running, with no "terminated unexpectedly" dialog and no new renderer process gone (reason: clean-exit lines in main.log.

What did not work

Restarting Cursor (the original poster). Choosing "New Window" in the dialog only repeats the error (a commenter).

Risks

Downgrading leaves you on an older build; turn updates back on once 3.19.13 or later is available (our inference).

Verified scope

Cursor 3.19.x before 3.19.13 on Linux (every report in the thread was on 3.19.7), September 2026.

Becomes obsolete when

3.19.x builds before 3.19.13 are no longer installed.

Related

• confusable #84