After running cursor for about 5 mins I can see a Git process in the activity monitor and within few seconds the memory shoots up to more than 20GB and freezes my laptop
On clicking on the Git process I can see this
Had to switch to vscode because of this issue
I don’t even have many vscode extensions
OS version:
MacOS: 15.4.1 (Sequoia)
M1 Pro
Cursor version:
Hey, do you have any Git extensions installed?
Nope, don’t have any extensions
The “extension-host” indicates that the issue is related to the extensions. To check this, try starting in safe mode: cursor --disable-extensions. If everything is fine, open Process Explorer to try to identify the problematic extension.
will try this
tried disabling extension, still crashed, but got this
/Library/Developer/CommandLineTools/usr/bin/git show --pretty=format:%s<|ENT|><|RY|>%b<|ENT|><|RY|>%an<|E...
Found some similar issues posted as well
I think @danperks can handle this.
@danperks please help
Hey, does this happen still if you run Cursor with extensions disabled?
To do this, go into a terminal and run cursor --disable-extensions.
I’d be surprised if this was Cursor doing this out the box, I’d think this was either a bad Git installation or a bad extension that’s causing this as my first guess.
yes it still happens, you can see my extensions here
I also encountered this problem
I am a subscriber of both cursor and trae.ai simultaneously
At first, I found on trae that macos would not respond after running and then the computer would restart automatically
The solution I attempted was to completely delete both cursor and trae (including the relevant content under ~).
Then I reinstalled cursor (without trae) and opened my golang project, only to find that the system crashed and restarted automatically
I observed abnormal CPU loads in go and gopls, with the highest reaching 500%
The following is the content in cursor’s “about”
Is there anyone who can help me
Version: 0.50.5 (Universal)
VSCode Version: 1.96.2
Commit: 96e5b01ca25f8fbd4c4c10bc69b15f6228c80770
Date: 2025-05-18T04:16:01.651Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
After updating to cursor version: 0.50.7 this issue seems to be fixed for me
I followed the following steps and did not reappear the problem [at the moment]
Remove all relevant content and reinstall
No plugins are installed. Currently, being in a plugin-free environment doesn’t affect my work
In my case, I particularly suspect the vs code go plugin is the cause
@ashley @danperks