Cursor Memory Leak? 7GB+ RAM Usage Makes It Unusable (Crashes Constantly)

Hi everyone,
I’m experiencing extreme memory usage in Cursor, leading to constant crashes. The main Cursor process + Cursor Helper (Renderer) combined are using over 7GB of RAM, which seems way too high for a code editor (see attached screenshot).

Issue Details:

Cursor’s memory usage keeps increasing over time until it reaches 7GB+ and crashes.

  • Even with no extensions installed and no large files open, RAM usage is extremely high.
  • I’ve tried restarting Cursor, but the issue persists.
  • When checking Activity Monitor, I see Cursor Helper (Renderer) is consuming more RAM than the main process.

What I’ve Tried:

:white_check_mark: Restarting Cursor
:white_check_mark: Running Cursor without extensions (I have none installed)
:white_check_mark: Checking for large open files (none are particularly large)
:white_check_mark: Attempting to launch Cursor with --disable-gpu --disable-crash-reporter (but the cursor command isn’t recognized)
:white_check_mark: Checking for updates (I’m on the latest version)

System Details:

  • MacBook Pro (14-inch, 2021)
  • Chip: Apple M1 Pro
  • Memory: 16GB RAM
  • macOS Version: Sequoia 15.3.1
  • Cursor Version: 0.46.9 (Universal)
  • VSCode Version: 1.96.2
  • Electron Version: 32.2.6
  • Chromium Version: 128.0.6613.186
  • Node.js Version: 20.18.1

Is anyone else experiencing this? Is this a known issue, or is there a way to limit Cursor’s memory usage? Any help would be appreciated!

Thanks!

Hey, does this happen with other projects as well? It might be related to having too many conversations in your chat history. Try opening a new project. The issue might also be connected to having Shadow Workspace enabled, try disabling it. If none of the above solves the problem, try clearing the cache.

Solution: Cursor Memory Leak & Crashes Fixed

After extensive troubleshooting, I’ve found a simple but effective solution to the memory leak issues causing Cursor to crash after consuming excessive RAM (7GB+).

Root Cause

The problem appears to be related to corrupted configuration files, not the project itself. Simply clearing the cache (as some suggest) isn’t sufficient to resolve the issue in all cases.

Complete Fix

Here’s the step-by-step solution that worked for me:

  1. Close Cursor completely

    • Ensure all Cursor processes are terminated
  2. Delete Cursor’s entire configuration directory

    • Run this command in Terminal: rm -rf ~/Library/Application\ Support/Cursor/
    • This removes all configuration files, not just the cache
  3. Restart Cursor

    • Launch Cursor from your Applications folder
  4. Set up as new

    • Choose “Start from Scratch” when prompted
    • Don’t import VS Code extensions initially
    • You can add essential extensions later if needed
  5. Monitor memory usage

    • Open your problematic project and observe memory usage

Additional Tips

If the problem returns:

  • Try disabling the “Codebase-wide” embedding feature (which computes embeddings for your codebase)
  • Check if Shadow Workspace is enabled and disable it (it’s known to increase memory usage)
  • Look for large files in your project that might trigger memory issues

This solution worked immediately after hours of unsuccessful troubleshooting with other methods. Hope it helps someone else!

I’m about to apply above solution… but seriously guys ?
PID RSS VSZ %MEM COMMAND
7563 361.6 MiB 77.4 GiB 1.1 /home/gus/.cursor-server/cli/servers/…
2232 229.3 MiB 73.5 GiB 0.7 /home/gus/.cursor-server/cli/servers/…
2189 96.8 MiB 11.3 GiB 0.3 /home/gus/.cursor-server/cli/servers/…
1769 70.7 MiB 953.3 MiB 0.2 /usr/sbin/unity-greeter
2257 62.9 MiB 11.2 GiB 0.1 /home/gus/.cursor-server/cli/servers/…
For anyone that wants to see their own results:

I experienced the same high memory usage issue with Cursor, where the Cursor Helper (Renderer) exceeded 5GB, eventually leading to crashes every time I opened the workspace. After some troubleshooting, I resolved the problem by deleting the repository folder and then re-cloning it from Git.

For context, I’m using the following setup on the same model and macOS version:

Cursor Version: 0.46.11

VSCode Version: 1.96.2

Commit: ae378be9dc2f5f1a6a1a220c6e25f9f03c8d4e10 (dated 2025-03-07T06:43:50.208Z)

Electron: 32.2.6

Chromium: 128.0.6613.186

Node.js: 20.18.1

V8: 12.8.374.38-electron.0

OS: Darwin arm64 24.3.0

I hope this helps anyone facing similar issues!