Git branch too big, can't view changes without crashing pc

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I am a noob to this whole thing. New of Git, push off setting it up.
Finally want to release versions of project.
Commit a Release version and am now looking forward to using git.
Any time I click on that branch, (worse it is currently the main branch) Cursor begins running console windows in background until theres a memory leak I assume. crashing my pc.

If I end the task early enough I can stop the pc from crashing.
Then I have to reopen cursor and close the git changes that haven’t loaded and kill the task again. Then I can open Cursor without crashing the pc until I try to view that branch again.

Any help would be great. I will answer any questions you may have as quickly as I can.

Steps to Reproduce

Any time I click on that branch that has 3364 files changed and 7039 insertions(+)
Not sure how as my project shouldn’t have that many files

Expected Behavior

I am meant to see the changelog in cursor, I think…

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.46 (system setup)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. Looks like SCM is crashing on a very large diff. Let’s narrow down the issue quickly:

Please check:

  • Run Cursor without extensions: from the command line, cursor --disable-extensions. Does the crash repeat?
  • Open CTRL+Shift+P > Developer: Open Process Explorer and take a screenshot of which process spikes (git.exe, extensionHost, Cursor.exe).
  • Open Help > Toggle Developer Tools and send errors from Console, plus the logs folder: CTRL+Shift+P > Developer: Open Logs Folder.
  • Temporary workaround: don’t open the Source Control tab for this branch; view changes via git diff in the terminal.
  • Check if build artifacts/large directories accidentally got into the repo (e.g., node_modules, dist, .next, etc.). If yes, add them to .gitignore and remove from index (git rm -r --cached …) to reduce the change volume.

Useful diagnostic steps here: Troubleshooting Guide | Cursor Docs

Also:

  • Enable extension monitoring: Settings > Application > Experimental > Extension Monitor Enabled, then CTRL+Shift+P > Developer: Open Extension Monitor and send a screenshot.
  • Clarify if the issue repeats in another repo or only in this one.

Please send: screenshot/video, reproduction steps, logs/console, list of extensions, and result of running without extensions.

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