Cursor high memory usage

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Cursor Helper plugin is consuming excessive CPU and causing the M4 Air to overheat, resulting in severe performance issues.

Steps to Reproduce

Open a new Cursor window or open any repository in Cursor, the CPU usage spikes immediately.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.26 (Universal)
VSCode Version: 1.105.1
Commit: f628a4761be40b8869ca61a6189cafd14756dff0
Date: 2025-11-24T05:39:06.655Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

Does this stop you from using Cursor

Yes - Cursor is unusable

With my Apple M3 as well, I’ve been noticing mega-lag. Unchecked quiet a few models but didnt help.

Hey, thanks for the report. I can see the Cursor Helper process is putting high load on the CPU on your M4 Air. Let’s run a few checks to figure out the cause.

Quick diagnostic steps:

  1. Test without extensions:
    Run in your terminal:
    cursor --disable-extensions
    Does the CPU spike still happen in this case?

  2. Check Process Explorer:
    CMD+Shift+P → “Developer: Open Process Explorer”
    Take a screenshot when the CPU usage spikes and share it here

  3. Try globalStorage cleanup (this often helps with memory and CPU issues in v2.0+):

    • Completely close Cursor
    • Press CMD+Shift+G in Finder
    • Go to: ~/Library/Application Support/Cursor/User/globalStorage/
    • Rename the files state.vscdb and state.vscdb.backup to *.old
    • Restart Cursor
  4. Check console errors:
    Help → Toggle Developer Tools → Console tab → take a screenshot of any errors, if there are any

It would also be helpful to know:

  1. Does this happen right after startup or only after certain actions?
  2. How large is your project/codebase?
  3. Have you installed any extensions recently?

@ChaVara, could you also try these steps and share your results?

Let me know what you find.

1 Like

Seems like it got resolved with step 3 followed by update to Version: 2.1.32

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.