sometimes rgArm processes and 100% CPU usage! #1341

lilianhua · 2024-03-22T09:20:04Z

Sometimes this problem occurs: rgArm processes and 100% CPU usage
Here's a screenshot of what happened.

and my computer configuration:

my cursor version:

Version: 0.30.3
VSCode Version: 1.86.2
Commit: 2e7179e3e051701daa9a88391f21ae69d01be4e0
Date: 2024-03-22T04:29:22.511Z
Electron: 27.2.3
ElectronBuildId: undefined
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.2.0

truell20 · 2024-03-22T18:11:15Z

Is this triggered by taking any actions in the editor? E.g. using Command + Shift + F?

lilianhua · 2024-03-25T03:14:00Z

Is this triggered by taking any actions in the editor? E.g. using Command + Shift + F?

I'm not sure either.
But it seems to happen when I disable or enable a plugin，for example I use codeium plugin.

lilianhua · 2024-03-28T03:44:26Z

When I update cursor, this problem will appear after the installation is complete.

John0x · 2024-05-20T08:11:01Z

Having the same issue with a nextjs project in the most recent version, it's making the whole IDE laggy

fossilet · 2024-06-28T09:12:30Z

any update? this renders cursor unusable..

gnakohet · 2024-07-03T01:33:12Z

Oops, same here.
I can't open files in my workspace of cursor. My mac is stucked because of "rgArm" from cursor, rgArm seems like so busy. I would get back to vscode if this is not resolved ;-(.

ciekawy · 2024-09-02T17:37:18Z

I found recently some 300 rgArm processes making my M3 pretty hot for the first time and lvg load 950.58 ;)

gerodp · 2024-09-11T11:46:28Z

I'm experiencing the same issue too :(

I'm using a Mac Pro M1 with Cursor:

Version: 0.40.4
VSCode Version: 1.91.1
Commit: 63dae81aea2c3fc079420fe72578a8eef26ba870
Date: 2024-09-05T02:52:05.660Z
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.6.0

tyfiero · 2024-09-14T00:13:15Z

This still happens with me too. I have a maxed out M3 MacBook and it still uses 100% CPU. Rendering cursor unusable :(

This feels like a pretty big issue, I feel like it should be elevated. Normally only happens for me when using the git panel in the UI, staging files and committing.

joshgachnang · 2024-09-27T15:48:12Z

This was happening to me every time I run Yarn. I tracked it down to the Auto Import plugin. I disabled plugins and kept wiping out node_modules while running this in another terminal. As soon as I had that plugin enabled, I started getting 200-1000 processes.

 rgwatch() {
   while true; do
     pgrep rg | wc -l;
     sleep 1
   done
 }

renatho · 2024-10-03T19:32:48Z

Same here. Also in vscode, but there it's the command rg instead of rgArm.

renatho · 2024-10-03T19:52:13Z

In VSCode I could stop the issue by clicking to stop the extension recommendations.

I couldn't fix it on Cursor, so I started removing some config files from the project (https://github.com/automattic/jetpack/) until it stopped. Then I reverted it and the issue didn't happen anymore. Hopefully, it will continue working well!

hserranome · 2024-10-14T08:18:24Z

Same here. It's making Cursor pretty unusable.

andres-blanco · 2024-10-14T18:59:58Z

me too. This started happening to me when updating to Version: 0.42.2

jonnysamps · 2024-10-17T20:56:13Z

Same thing here

KKonstantinov · 2024-10-28T13:25:48Z

This is not related to Cursor directly. Looks like VS Code is using this library for recursive searching, which is causing the issue: https://github.com/BurntSushi/ripgrep

Add the following config to your workspace config and Cursor should start working like a charm.

Make sure you include any dependency folders (e.g. node_modules in this example if your code is Javascript) in, as well as any build directories.

        "search.followSymlinks": false,
        "files.exclude": {
            "**/tmp/**": true,
            "**/node_modules/**": true,
            "**/.git/objects/**": true
        },
        "files.watcherExclude": {
            "**/.git/objects/**": true,
            "**/.git/subtree-cache/**": true,
            "**/node_modules/**": true,
            "**/tmp/**": true,
            "**/dist/**": true
        },
        "search.exclude": {
            "**/node_modules/**": true,
            "**/dist/**": true,
            "**/tmp/**": true,
            "**/.git/objects/**": true,
            "**/.git/subtree-cache/**": true
        }

accolver · 2024-11-27T19:29:46Z

I was able to use the Process Explorer in Cursor to identify the command. For me it was the Tailwind CSS IntelliSense extension running

/Applications/Cursor.app/Contents/Resources/app/node_modules.asar.unpacked/@vscode/ripgrep/bin/rgArm --files --hidden --case-sensitive --no-require-git -g **/{tailwind,tailwind.config,tailwind.*.config,tailwind.config.*}.{js,cjs,ts,mjs,mts,cts} -g !**/.git -g !**/.svn -g !**/.hg -g !**/CVS -g !**/.DS_Store -g !**/Thumbs.db -g !**/tmp/** -g !**/node_modules/** -g !**/.git/objects/** -g !/{**/.git,**/.svn,**/.hg,**/CVS,**/.DS_Store,**/Thumbs.db,**/tmp/**,**/node_modules/**,**/.git/objects/**,**/.git/**,**/node_modules/**,**/.hg/**,**/.svn/**} --no-ignore --no-config --no-ignore-global

The fix was to either

Uninstall the Tailwind CSS IntelliSense extension
Hover over the "Disable" button dropdown and install a previous version. v0.10.5 worked for me

rlirli · 2024-11-29T22:48:55Z

The solution suggested by @KKonstantinov completely resolved the excessive rgArm process spawning when using Cursor on my M1 Mac — many, many thanks! Precautiously, I also excluded"/.turbo/" and "/.next/" from the file watcher for my Next.js project.

Interestingly, I never encountered this process overload in VS Code, where I have the same extensions installed.

chomama05 · 2024-11-30T14:57:53Z

@accolver Thank you so much for your comment. I searched for hours and luckily fell on this issue. Uninstalling the Tailwind extension magically solved all my issues.

I am on M3 pro and my CPU usage was at ~93% and there were hundreds of threads for "rgArm". Since I removed the Tailwind extension I am back to ~15% CPU usage and no more "rgArm" threads :)

musab-mk · 2024-12-03T06:14:39Z

Uninstalling the Tailwind extension also fixed my problem!

FilipPyrek · 2024-12-09T14:44:03Z

Sam here, uninstalling Tailwind extension fixed the problem for me.

jeffreylouden · 2024-12-10T19:30:48Z

uninstalling Tailwind fixed it, but after updating cursor this morning, the issue has resurfaced even with the Tailwind extension removed.

jjh42 · 2024-12-13T02:26:05Z

I'm also experiencing this. cursor 0.43.6. Removing tailwind seems to have helped, but tailwind extension works fine in vs code.

max-winderbaum · 2024-12-18T19:32:58Z

This is making Cursor pretty unusable for me, I'm trying everything I know how to do but nothing's sticking yet. Many, many ~100 rgArm processes are eating my computer alive.

They all seem to spin up at once after working fine for a while, I'm trying to determine a repro / some reason now but it's slow as I'm trying to do my regular job

Ulanxx · 2024-12-19T09:59:01Z

Same with me, in 0.43.6.

Ulanxx · 2024-12-19T11:41:16Z

This is not related to Cursor directly. Looks like VS Code is using this library for recursive searching, which is causing the issue: https://github.com/BurntSushi/ripgrep

Add the following config to your workspace config and Cursor should start working like a charm.

Make sure you include any dependency folders (e.g. node_modules in this example if your code is Javascript) in, as well as any build directories.

        "search.followSymlinks": false,
        "files.exclude": {
            "**/tmp/**": true,
            "**/node_modules/**": true,
            "**/.git/objects/**": true
        },
        "files.watcherExclude": {
            "**/.git/objects/**": true,
            "**/.git/subtree-cache/**": true,
            "**/node_modules/**": true,
            "**/tmp/**": true,
            "**/dist/**": true
        },
        "search.exclude": {
            "**/node_modules/**": true,
            "**/dist/**": true,
            "**/tmp/**": true,
            "**/.git/objects/**": true,
            "**/.git/subtree-cache/**": true
        }

Thank you very much, uninstalling the Tailwind plugin did not solve my problem, but the answer from this guy solved it.

crow-1412 · 2024-12-24T08:16:33Z

This is not related to Cursor directly. Looks like VS Code is using this library for recursive searching, which is causing the issue: https://github.com/BurntSushi/ripgrep

Add the following config to your workspace config and Cursor should start working like a charm.

Make sure you include any dependency folders (e.g. node_modules in this example if your code is Javascript) in, as well as any build directories.

        "search.followSymlinks": false,
        "files.exclude": {
            "**/tmp/**": true,
            "**/node_modules/**": true,
            "**/.git/objects/**": true
        },
        "files.watcherExclude": {
            "**/.git/objects/**": true,
            "**/.git/subtree-cache/**": true,
            "**/node_modules/**": true,
            "**/tmp/**": true,
            "**/dist/**": true
        },
        "search.exclude": {
            "**/node_modules/**": true,
            "**/dist/**": true,
            "**/tmp/**": true,
            "**/.git/objects/**": true,
            "**/.git/subtree-cache/**": true
        }

thanks my bro, this helps me a lot.

willshw · 2025-01-14T23:02:22Z

This is making Cursor pretty unusable for me, I'm trying everything I know how to do but nothing's sticking yet. Many, many ~100 rgArm processes are eating my computer alive.

They all seem to spin up at once after working fine for a while, I'm trying to determine a repro / some reason now but it's slow as I'm trying to do my regular job

Same thing happens to me on my MacBook Pro. I mostly work with Python repos. The setting suggested above doesn't work for me and I added some Python related paths, no luck. The rgArm processes just slow everything down and it happened quite frequently. I feel like it happens whenever I save files. If there are a lot of changes in the code, lots of rgArm processes were spawned.

ZachMoreno · 2025-01-16T16:42:35Z

Love Cursor, thanks for working hard to make it great!

My M2 MBP was pegged at 💯 with Cursor open, found this thread after googling rgArm, killed Cursor and now I'm at 24%

suvmusik · 2025-01-19T01:22:43Z

This is not related to Cursor directly. Looks like VS Code is using this library for recursive searching, which is causing the issue: https://github.com/BurntSushi/ripgrep

Add the following config to your workspace config and Cursor should start working like a charm.

Make sure you include any dependency folders (e.g. node_modules in this example if your code is Javascript) in, as well as any build directories.
    "search.followSymlinks": false,
    "files.exclude": {
        "**/tmp/**": true,
        "**/node_modules/**": true,
        "**/.git/objects/**": true
    },
    "files.watcherExclude": {
        "**/.git/objects/**": true,
        "**/.git/subtree-cache/**": true,
        "**/node_modules/**": true,
        "**/tmp/**": true,
        "**/dist/**": true
    },
    "search.exclude": {
        "**/node_modules/**": true,
        "**/dist/**": true,
        "**/tmp/**": true,
        "**/.git/objects/**": true,
        "**/.git/subtree-cache/**": true
    }

Where do I paste this? Newbe here...

dragosrotaru · 2025-01-23T16:25:52Z

Same with me. I have Like 20+ agArm processes running. I can barely use my computer and I've got a Macbook pro M2 max. I kill cursor and boom it goes away

abegehr · 2025-01-24T15:34:54Z

For me, the TailwindCSS plugin was also the issue. Disabling it solves it. There are a few issues open on https://github.com/tailwindlabs/tailwindcss-intellisense regarding this, however no traction from @tailwindlabs: tailwindlabs/tailwindcss-intellisense#1109

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

sometimes rgArm processes and 100% CPU usage! #1341

sometimes rgArm processes and 100% CPU usage! #1341

lilianhua commented Mar 22, 2024

truell20 commented Mar 22, 2024

lilianhua commented Mar 25, 2024

lilianhua commented Mar 28, 2024

John0x commented May 20, 2024

fossilet commented Jun 28, 2024

gnakohet commented Jul 3, 2024

ciekawy commented Sep 2, 2024

gerodp commented Sep 11, 2024

tyfiero commented Sep 14, 2024

joshgachnang commented Sep 27, 2024 •

edited

Loading

renatho commented Oct 3, 2024

renatho commented Oct 3, 2024

hserranome commented Oct 14, 2024

andres-blanco commented Oct 14, 2024

jonnysamps commented Oct 17, 2024

KKonstantinov commented Oct 28, 2024 •

edited

Loading

accolver commented Nov 27, 2024 •

edited

Loading

rlirli commented Nov 29, 2024

chomama05 commented Nov 30, 2024

musab-mk commented Dec 3, 2024

FilipPyrek commented Dec 9, 2024 •

edited

Loading

jeffreylouden commented Dec 10, 2024

jjh42 commented Dec 13, 2024 •

edited

Loading

max-winderbaum commented Dec 18, 2024 •

edited

Loading

Ulanxx commented Dec 19, 2024

Ulanxx commented Dec 19, 2024 •

edited

Loading

crow-1412 commented Dec 24, 2024

willshw commented Jan 14, 2025

ZachMoreno commented Jan 16, 2025

suvmusik commented Jan 19, 2025

dragosrotaru commented Jan 23, 2025 •

edited

Loading

abegehr commented Jan 24, 2025 •

edited

Loading

sometimes rgArm processes and 100% CPU usage! #1341

sometimes rgArm processes and 100% CPU usage! #1341

Comments

lilianhua commented Mar 22, 2024

truell20 commented Mar 22, 2024

lilianhua commented Mar 25, 2024

lilianhua commented Mar 28, 2024

John0x commented May 20, 2024

fossilet commented Jun 28, 2024

gnakohet commented Jul 3, 2024

ciekawy commented Sep 2, 2024

gerodp commented Sep 11, 2024

tyfiero commented Sep 14, 2024

joshgachnang commented Sep 27, 2024 • edited Loading

renatho commented Oct 3, 2024

renatho commented Oct 3, 2024

hserranome commented Oct 14, 2024

andres-blanco commented Oct 14, 2024

jonnysamps commented Oct 17, 2024

KKonstantinov commented Oct 28, 2024 • edited Loading

accolver commented Nov 27, 2024 • edited Loading

rlirli commented Nov 29, 2024

chomama05 commented Nov 30, 2024

musab-mk commented Dec 3, 2024

FilipPyrek commented Dec 9, 2024 • edited Loading

jeffreylouden commented Dec 10, 2024

jjh42 commented Dec 13, 2024 • edited Loading

max-winderbaum commented Dec 18, 2024 • edited Loading

Ulanxx commented Dec 19, 2024

Ulanxx commented Dec 19, 2024 • edited Loading

crow-1412 commented Dec 24, 2024

willshw commented Jan 14, 2025

ZachMoreno commented Jan 16, 2025

suvmusik commented Jan 19, 2025

dragosrotaru commented Jan 23, 2025 • edited Loading

abegehr commented Jan 24, 2025 • edited Loading

joshgachnang commented Sep 27, 2024 •

edited

Loading

KKonstantinov commented Oct 28, 2024 •

edited

Loading

accolver commented Nov 27, 2024 •

edited

Loading

FilipPyrek commented Dec 9, 2024 •

edited

Loading

jjh42 commented Dec 13, 2024 •

edited

Loading

max-winderbaum commented Dec 18, 2024 •

edited

Loading

Ulanxx commented Dec 19, 2024 •

edited

Loading

dragosrotaru commented Jan 23, 2025 •

edited

Loading

abegehr commented Jan 24, 2025 •

edited

Loading