Excessive CPU Usage on M3 Mac

Bug Report
1

I have been noticing an unacceptable CPU usage on Cursor across multiple macs. The task that is responsible for lint or file sync or somehow watching the file system using ripgrep (rgArm) consumes every available CPU core on my machine jumping to over a 1000% CPU usage.

Ultimately I end up having to kill or renice or forcibly find the following task in the Cursor.app file and removing execution rights because it simply uses too much CPU power.

Contents/Resources/app/node_modules.asar.unpacked/@vscode/ripgrep/bin/rgArm

Sadly, doing this, limits file search, TS server completion, es-lint and many other capapbilities in the IDE that rely on indexing of the file system. It’s fine to have some processes in the background but it will literally cut hours out of usability on a M3 16" MBP and reduce my ability to do anything else computationally heavy.

This is unacceptable and is making me seek other IDEs/editors after finally finding a happy home here. Please help.

2 Likes
2

Yup - this problem has basically made Cursor unusable for me too.

3

Hey @gabrieljbaker,

Check this topic:

4

That’s helpful @deanrie thanks! But I sort of rely on the eslint extension, as does everyone on my team. Any other ideas?

5

Nope, you can disable extensions one by one.

6

I have a dream where I can both lint my code and use cursor at the same time (heh)

7

Could you post a screenshot from the Process Explorer under command palette

8

@tmm1

image
image1338×866 105 KB

9

Sorry I’m asking for the Process Explorer feature inside cursor

11

I have the same problem all the time. Cursor process is always on 180% CPU on my Mac (M2).
Here is the screenshot of the Cursor process explorer:
(The extension 2 process is always between 160 to 220)

Screenshot 2024-10-03 at 7.07.53 PM
Screenshot 2024-10-03 at 7.07.53 PM1594×1016 187 KB

12

This problem still persists and can be consistently reproduced when using the CMD + SHIFT + F shortcut to search across files.

The issue can’t be reproduced on VS Code 1.92.1 (Universal).

I am using a MacBook Pro M2 Max with macOS Sequoia Version 15.0 (24A335).

Cursor Information:

Cursor Version: 0.42.2
VSCode Version: 1.93.1
Commit: c499aee5f16e67815c7dc795ff338dc8ab3e07f0
Date: 2024-10-12T05:39:54.471Z
Electron: 30.4.0
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.0.0
13

It seems that many people have already talked about this issue. The members of the Cursor team keep asking users to recheck extensions or even delete certain ones like ESLint. ESLint is a very important extension that almost all teams are using, and it works perfectly fine on VS Code. This is quite confusing. It’s likely that many users will consider switching to another platform because of this issue.

14

By the way, this also happens in VSCode, and you can see these complaints on GitHub. We don’t recommend disabling your extensions. Instead, try to find the cause of the issue, as it might not even be the ESLint extension. First, check the logs and Process Explorer to identify the problem.