Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Cursor frequently crashes on Windows due to the renderer process continuously increasing memory usage and eventually exceeding ~4GB. Once the renderer process reaches around 4GB of memory, Cursor becomes unresponsive or crashes.
The issue appears to be related to a memory leak in the renderer / webview / Electron process. Memory usage keeps growing over time and does not get released, even during normal editing workflows.
Steps to Reproduce
- Launch Cursor on Windows.
- Open a project (medium or large repository).
- Use Cursor normally (editing files, navigating, optionally using Cursor AI features).
- Keep Cursor running for some time (minutes to hours).
- Monitor processes in Task Manager.
Observed result:
- The Cursor renderer process (–type=renderer) keeps increasing memory usage.
- Memory eventually exceeds ~4GB.
- Cursor crashes or becomes unresponsive.
Expected Behavior
The renderer process should have stable memory usage over time.
Memory should be released when files or webviews are no longer in use.
Cursor should remain stable during long-running development sessions without crashing due to excessive memory usage.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.2.43 (system setup)
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
For AI issues: which model did you use?
opus4.5
Does this stop you from using Cursor
Yes - Cursor is unusable
