After updating Cursor from 3.18.25 to 3.19.7 using the official APT repository, I started experiencing serious stability issues that were not present before.
Environment:
OS: Ubuntu 26.04 (64-bit)
Installed via: Official Cursor APT repository
Previous version: 3.18.25
Updated version: 3.19.7
Issues observed after the update:
Cursor consumes significantly more RAM than before.
The application occasionally closes unexpectedly.
Sometimes I get the message:
“The window terminated unexpectedly (reason: ‘clean-exit’, code: ‘0’)”
I initially noticed this while using Agent mode, but later it also happened without starting any Agent session.
Troubleshooting:
Restarted Cursor.
Checked system logs for OOM kills but didn’t find any evidence that Linux was terminating the process.
Downgraded back to Cursor 3.18.25.
Result:
After downgrading to 3.18.25, the problem disappeared. Memory usage returned to normal and the unexpected window termination no longer occurs.
This looks like a regression introduced in 3.19.7. Let me know if you need any additional logs or information to help investigate.
Hey @bharat, thanks for the detailed report, and for confirming that downgrading to 3.18.25 clears it.
This is a known issue we are already tracking. It is specific to Linux on 3.19.x: a change in the runtime (Electorn) we ship in 3.19 can make the window process exit cleanly (that “clean-exit, code 0” message) and use more memory than before. Windows and macOS should not be affected. I have added your report to the internal tracking.
A fix is in progress and will ship in an upcoming release.
@anishkumar Our expectation is that this only affects Linux. Are you seeing the exact same symptoms (“The window terminated unexpectedly (reason: ‘clean-exit’, code: ‘0’)”)?
I’m experiencing a serious performance/memory issue with the latest Cursor update on Windows 11.
Here’s what happened:
I gave a prompt to the Agent, and shortly after that, Cursor’s memory usage started increasing rapidly, going above 15 GB.
Cursor became completely unresponsive, so I had to force-close it using Task Manager.
I reopened Cursor and gave the same prompt again in the Agent window, and the exact same issue happened.
At one point, the Agent prompt/input window became so laggy that I couldn’t even type properly.
Eventually, the entire Cursor IDE froze and started affecting other applications as well. Even Chrome became unresponsive, and my local development server also started hanging.
Cursor was consuming extremely high CPU and memory.
As soon as I force-closed Cursor from Task Manager, everything went back to normal.
The problem consistently occurs when Cursor is running, and disappears immediately after closing it.
I also downloaded and tested an older version of Cursor, and the older version does not have this issue.
This makes me think there may be a regression or memory/CPU leak in the latest Cursor update, particularly related to the Agent.
I’m running Windows 11.
Please investigate this, as the issue is severe enough to make the entire system unstable and unusable while Cursor is running.
Hey @Neureon.Group, thanks for the report, and sorry about that.
This is a known issue we are already tracking. It is specific to Linux on 3.19.x: a change in the runtime we ship in 3.19 can make the window process exit right after launch (that “clean-exit, code 0” message).
The reliable workaround for now is to go back to 3.18.25 (Cursor · Download), the version you were on before, and pause updates until the fix ships.
Cursor loads and throws an error that the window terminated unexpectedly reason: ‘clean-exit’. Choosing to close exits app. Choosing New Window causes a repeat and loop of the issue. I’m using the agent window.
Grokbot was able to get me working:
disable-hardware-acceleration in ~/.cursor/argv.json
menu/launcher flags --disable-gpu --ozone-platform=x11 in ~/.local/share/applications/cursor.desktop
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.
in windows 11 laptop still have this issue with latest version of cursor. ram size increasing.
and cursor ide inside window showing black screen.
and sorry i by mistake i skiped the caputring cursor ram useage. its ram usage is 10GB + and increasing.
after force stop from task manager by kill cursor if use then normally again works around 1,2 gb max.
after long running cursor 1-2 hours after again start doing behave like this increasing memory it’s happen i think when my laptop IDLE when im not using for laptop that thing i have notice.
Unless you’re seeing CodeWindow: renderer process gone (reason: clean-exit, code: ) on Linux, this is likely a new issue and I suggest raising a new thread!
