SIGSEGV crash on Source Control actions + broken Git/UI state when Cursor Worktree window is open (multi-root workspace, 3 machines)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

SIGSEGV crash on Source Control actions + broken Git/UI state when Cursor Worktree window is open (multi-root workspace, 3 machines)

Where does the bug appear (feature/product)?

Cursor IDE — Source Control panel, Cursor-managed Worktree windows, multi-root workspace

Describe the Bug

On three separate machines (same workflow), Cursor crashes completely (process exits) when I use Source Control in a multi-root workspace with multiple Git repositories — especially when clicking Commit or Discard/Revert changes.
Additionally, when I open Cursor with a Cursor Worktree window already open alongside the main workspace, the IDE does not load workspace state correctly: Git status, language mode, and branch information are wrong or missing. The only reliable workaround is to close the Worktree window, fully quit Cursor, and reopen the workspace.
This is not a Git repository problem: git commands succeed in the extension logs right before the crash. The failure is a native SIGSEGV in the Electron process.

Steps to Reproduce

  1. Open a multi-root workspace with 5 separate Git repositories (5 folders, each its own .git).
  2. Optionally have a Cursor Worktree window open (managed under ~/.cursor/worktrees).
  3. Open Source Control and review pending changes across repos.
  4. Click Commit or Discard on a changed file.
  5. Expected: commit/discard completes.
  6. Actual: Cursor crashes and closes. On Linux, coredumpctl shows SIGSEGV.
    Secondary reproduction (state corruption):
  7. Open workspace while a Worktree window is still open from a previous session.
  8. Observe: branch name, Git changes, and language detection are incorrect or empty.
  9. Close Worktree window → quit Cursor completely → reopen workspace.
  10. State loads correctly until a Worktree window is opened again.

Expected Behavior

  • Source Control actions should not crash the IDE.
  • Worktree windows should not break Git/language/branch detection in the main workspace.
  • No full application restart should be required to restore SCM state.

Operating System

Linux

Version Information

  • OS: Linux (Garuda/Arch), kernel 7.0.9-zen
  • Cursor: 3.5.17 (stable), commit d5b2fc092e16007956c9e5047f76097b9e626ca0, x64
  • Install: cursor-bin (AUR) using system electron42
  • Git: 2.54.0 at /usr/bin/git
  • Workspace: multi-root, 5 repos on local ext4 (not network FS)
  • Projects: separate repos (not classic git worktree checkouts); Cursor Worktree feature is used for agents

Coredumps (Linux):

coredumpctl list cursor
TIME                          PID   SIG
Fri 2026-05-22 08:23:11 -03   24454 SIGSEGV
Fri 2026-05-22 08:27:35 -03   33148 SIGSEGV
Fri 2026-05-22 08:34:27 -03   38724 SIGSEGV
Fri 2026-05-22 08:43:58 -03   50335 SIGSEGV

### For AI issues: which model did you use?
sonnet 4.6, Auto, Opus 4.6





### Does this stop you from using Cursor
No - Cursor works, but with this issue
5

Hey, thanks for the detailed report with the coredumps, it makes the issue obvious.

The root cause is the Electron versions. Cursor 3.5.17 is built against Electron 39.8.1, but cursor-bin from AUR runs the binary using system electron42. That’s a 3 major version gap, so the ABI isn’t compatible, and you get native SIGSEGV crashes in the Electron process during any heavy UI actions like Source Control, Worktree windows, or modal dialogs.

The broken Git, branch, and language state is a side effect of the crashes. Cursor saves workspace state to state.vscdb on a normal exit, but a SIGSEGV bypasses that, so on the next launch it loads stale state.

Two ways to fix it:

  1. Install electron39 from AUR and patch the cursor-bin wrapper so it uses that specific version instead of the generic electron. This thread covers the exact same case: Arch/CachyOS: opening modal/overlay windows crashes Cursor when cursor-bin uses generic system Electron; fixed by pinning wrapper to electron39
  2. Switch to the official AppImage or tarball from Cursor · Download. It bundles the correct Electron version, so there’s no system dependency.

This isn’t a Cursor bug. It’s an issue with the community maintained package. Let me know if it still crashes after switching, and we can dig deeper.

6

Patched cursor-bin wrapper to electron39 — confirmed running /usr/lib/electron39/electron, no SIGSEGV since. SCM commit/discard works again. Thanks!