Hey, thanks for the report. Memory gradually climbing to 100% and not freeing after you close Cursor is a known pattern on Windows. It’s usually caused by either a memory leak in the renderer process, extension host processes not shutting down properly, or both.
Let’s figure out what’s happening in your case:
-
Open Process Explorer:
Ctrl+Shift+P> “Developer: Open Process Explorer”- Check which process is using the memory (renderer, extensionHost, ptyHost, etc.).
- If you can, share a screenshot.
-
Check for OTEL errors:
Ctrl+Shift+P> “Developer: Toggle Developer Tools” > Console tab- Look for
[otel.error]orOTLPExporterErrorlines. - If you see them, that’s a known memory leak.
- Look for
-
Test without extensions: run
cursor --disable-extensionsin a terminal and see if the leak still happens. -
After closing Cursor, open Task Manager and check if any Cursor-related processes are still running. If yes, that would explain why RAM doesn’t free up.
Related threads with the same issue:
- Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans
- Renderer OOM crash (code -536870904) every ~3 minutes on Windows — 128GB RAM, reproducible
Let me know what you find and we’ll go from there.