CPU usage on idle

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor lost it. Even after updating the IDE and disabling all extensions, it exhibits extremely high CPU usage and spikes. See screenshots. Please advise how to enable some verbose logging to see exactly what tools are being used and what’s going on in there. WiFi is relatively quiet. I don’t think it’s doing much there. And yes, this is going on for hours. Not a simple “startup” issue. It’s been like this all day today. Same project as yesterday. Heck, it even happens when I close all projects & files and am sitting with an empty IDE. Screenshot for that too.

Steps to Reproduce

Start Cursor.

Expected Behavior

CPU should be idle.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.52 (user setup)
VSCode Version: 1.99.3
Commit: 9675251a06b1314d50ff34b0cbe5109b78f848c0
Date: 2025-10-17T01:41:03.967Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. Since you’ve already disabled extensions, let’s figure out which process is causing the CPU spike.

Please run these diagnostics:

  • Open Process Explorer: press Ctrl + Shift + P → type “Developer: Open Process Explorer”

  • Check which processes show high CPU (extensionHost, ptyHost, main, etc.)

  • Take a screenshot and share it here

  • Check Developer Console: Ctrl + Shift + P → “Developer: Toggle Developer Tools”

  • Look for any errors or warnings in the Console tab

  • View Logs: Ctrl + Shift + P → “Developer: Open Logs Folder”

  • Check recent log files for errors

Also try:

  • Launch Cursor from the command line: cursor --disable-extensions
  • Launch without GPU: cursor --disable-gpu
  • If a terminal is open, close all terminal instances and see if CPU usage drops

Once we see the Process Explorer data, we can pinpoint the cause.

Let me know what you find.

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