Cursor CPU usage causes lags

Bug Report
1

I’ve been asking about this issue on Reddit some time ago, but no response.

Is there any reason why cursor starts to lag and have excessive CPU usage after prolonged session? Why closing and reopening it resolves the issue, but only temporarily?

This happens even when I’m not using terminal in Cursor or any AI
Screenshot 2025-02-05 at 15.16.42

2

just curious if you have experienced similar behavior from VSCODE

3

In my case, the issues are (combined):

  • CPU Behavior: abnormal multi-core utilization (not 100% but sustained high load)
  • Network Patterns: network spikes of data being downloaded at about 6+Mb/s

Happens when agents are facing code errors and they are not being able to find a solution easily;
when i scroll back the COMPOSER chat and im reading the exactly same temptatives of the agents trying to fix the errors.

Standard Electron App Patterns

Renderer Process Dominance:
Known Electron architecture where:

  • Renderer handles UI/chat history parsing
  • GPU Process manages compositing (stable here = rendering isn’t the bottleneck)
  • IPC Overhead:
    Common in agent systems where postMessage communicates between:
    – Main process (Node.js) ↔ Renderer process (Chromium)

Inferred Technical Relationships

Memory Spikes:

  • Lag during chat navigation → Likely retained agent context objects in:
  • Composer’s React state
  • VSCode extension host memory

Network ↔ CPU Lockstep:

  • In my case: data download spikes concises with CPU increases indicating serialized agent states being transferred/rehydrated.
  • Mapped to WebSocket/API transfers during agent recomputes (Electron patterns)

Environment:

  • OS: Linux Mint “Mia”
    • Kernel: Linux x64 6.8.0-52-generic
  • Cursor Details:
    • Version: 0.45.9
    • VSCode Version: 1.96.2
    • Commit: cce0110ca40ceb61e76ecea08d24210123895320
    • Date: 2025-02-02T06:44:49.761Z
    • Electron: 32.2.6
    • Chromium: 128.0.6613.186
    • Node.js: 20.18.1
    • V8: 12.8.374.38-electron.0
  • Agents: Three agents operating concurrently:
    • Project Manager: Enforces guidelines and manages overall process flow. May trigger extra processing in the Composer.
    • Coder: Implements code changes and occasionally questions guidelines.
    • Error/Debug Specialist: Identifies and resolves errors while suggesting improvements or workarounds.
  • Hardware: Notebook with a Ryzen 7 (16 threads)
4

I, not a bot. Im just a guy with ADHD lol

5

@Graphie Here does not fix anything closing but only happens while im actively doing something on COMPOSER and don’t even need to be actively coding.

@Raphael909 I think its indirectly (kinda) with Agents and COMPOSED too and VS Code does not have it but it lags a lot with Cybercoder when the code reaches 1500+ lines