Segmentation fault (SIGSEGV / SIGABRT) — page 2
The process died at the native layer rather than throwing a JS error.
289 issues · 79 open · 210 resolved (73%) · first seen Apr 14, 2025
First response · local
What to do now
Most likely: The local Claude Code process crashed while parsing or executing.
- Record the Claude Code version and the first stack frame before restarting.
- Try a fresh session with the same minimal input to distinguish corrupted state from a repeatable crash.
- Preserve logs and compare reports from the same version before downgrading.
These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.
Is this getting better or worse?
This class of problem is still growing. 125 new reports in the last 90 days vs 68 in the 90 before — +84%. The open backlog peaked at 79 in 2026-08 and sits at 79 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
205 of these reports name the Claude Code build they were running, spanning 106 releases. Heaviest reporters:
- Claude Code v2.1.241
- Claude Code v2.1.139
- Claude Code v2.1.220
- Claude Code v2.1.112
- Claude Code v2.1.150
- Claude Code v2.1.50
- Claude Code v2.1.205
- Claude Code v2.1.170
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 29 days across 210 closures. Of the 210 closures with a recorded reason, 12% were closed as completed and 185 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
97 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] 2.1.243 Segmentation fault
- …or export introduced in 2.1.242 is also present in 2.1.243. Workaround Running 2.1.241 directly works. Repointing the launcher to 2.1.241 and temporarily disabling auto-update also restores operation: This report intenti…
Found in the thread of #89360 · resolved - [BUG] npm install now ships Bun binary (v2.1.126) — npm workaround for non-AVX VPS is dead, no upgrade path
- …oint. This means the npm installation path — the documented workaround for non-AVX environments — no longer works. I am a paying subscriber using Claude Code professionally for server administration and development acros…
Found in the description of #55520 · still open - [BUG] v2.1.242 segfaults on every launch (even `--version`) — interposed mimalloc `free` has no NULL check, glibc `newlocale` calls `free(NULL)` pre-main; v2.1.241 unaffected
- …ator symbols exported by each build Recovery Confirming the workaround in the report: repointing to 2.1.241 and setting in restores a working CLI.
Found in the thread of #89334 · still open - 2.1.243 native build segfaults instantly on startup: interposed free() crashes on free(NULL) from glibc 2.44 newlocale
- …duce On a glibc 2.44 system (e.g. up-to-date Arch/CachyOS): Workaround plus pinning in : (Note: repoints the symlink back at the broken build, so the auto-updater re-breaks the install until pinned.) Possibly related 842…
Found in the description of #89369 · still open - [BUG] Claude Code 2.1.243 immediately segfaults on Arch Linux x86_64
- Same crash here, adding details + a workaround since the original report has none. Environment - Claude Code 2.1.243 , native install ( , sha256 , 377,568,472 bytes) - Arch Linux, kernel 7.1.8-arch1-3, x86 64, glibc 2.44…
Found in the thread of #89393 · still open
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 101–200
Ranked by community engagement (reactions weighted over comments).
- Korean text causes crash (UTF-8 byte boundary error)
- [BUG]
- [BUG] Crash: HTTP Client thread SIGABRT (abort() called) in v2.0.69
- [BUG] Claude Code 2.1.217 crashes with General Protection Fault on VirtualBox (Kubuntu 26.04)
- iOS Simulator panel unusable on Xcode 27: hardcoded PrivateFrameworks path + Metal abort in claude-ios-sim helper
- [BUG] Bun v1.4.0 segfault at 0xFFFFFFFFFFFFFFFF ~30 min into remote-bridged session - 'exited with code 3' (Windows 11 26200, CC 2.1.209)
- [BUG] Claude Code app bundle lacks NSBluetoothAlwaysUsageDescription — child processes get hard-killed instead of prompted with Routines
- [BUG] Claude Code process exited with code 3
- [BUG]Failed to start Claude's workspace
- [BUG] Segmentation fault
- [BUG]
- [BUG] Cowork crashes with "Claude Code process exited with code 3" — Bun segfault inside VM on Windows 11 Enterprise
- [BUG] AVX detection issue on c7i.xlarge instance preventing execution
- [BUG] --worktree flag panics with segfault when .claude/worktrees directory already exists
- [BUG] Cowork - Claude Code process exits with code 139 (SIGSEGV) on launch
- [BUG] Segmentation fault right after Claude Code session start
- [BUG] Illegal Instruction in 2.1.77
- [BUG] illegal hardware instruction - bun has crashed (segfault)
- [BUG] [Windows] Claude Code crashes with segfault after ~9 min — canary Bun embedded in auto-updated claude.exe
- [BUG] Cowork: Intermittent "Segmentation fault" on task startup (macOS)
- [BUG] JavaScript heap OOM crash on long sessions — unbounded in-memory message accumulation
- [BUG]
- Segmentation fault crash on Windows x64 (Bun v1.3.5)
- [BUG] Shell snapshot creation causes 30-90 second delay per Bash command on Windows, only PC reboot helps
- Segmentation fault when quitting during MCP operation
- [Bug] Segmentation fault during Claude Code execution on macOS Silicon
- Crash: HTTP Client thread SIGABRT (abort() called) in v2.0.69
- [Bug] Segmentation fault in Bun runtime on Windows during Claude Code execution
- [BUG] Claude Code CLI: TypeError - codePointAt() Called on Undefined Segment
- [BUG] Installer crash (Bun has crashed)
- [BUG] Segmentation fault (core dumped)
- [BUG] Crashes on start-up on Fedora 42
- 2.1.243 SIGSEGV on startup (glibc 2.44, Arch) — self-heal to 2.1.241 worked, adding correlated repro
- claude --version segfaults (SIGSEGV) immediately on 2.1.243 — 2.1.241 works fine on same system
- 2.1.206 linux-x64 ships a Bun baseline build that segfaults on startup (glibc 2.41)
- panic(main thread): Segmentation fault at address 0x1269432E492
- SIGILL panic at identical binary offset chain (+0x2905212) across v2.1.168–v2.1.170 on one Linux machine; identical sibling machines unaffected
- [BUG] Claude Desktop for Windows (vs 1.11847.5 de 9 de junho de 2026): Claude Code process exited with code 3
- Recurring SIGILL/segfault in JSC GC (CodeBlockSet::clearCurrentlyExecutingAndRemoveDeadCodeBlocks) — bun 1.3.14
- [BUG] Claude Code process exited with code 3
- [Bug] claude CLI silently exits on transient network errors during tool-use turns (no retry, no backoff)
- Claude Code 2.1.113+ crashes on startup (SIGILL in bundled Bun 1.3.14) on Intel Emerald Rapids / Ubuntu 24.04
- Claude Code 2.1.149 crashes on launch — Bun v1.3.14 SIGILL/segfault on Intel macOS (x64)
- [BUG] bash: Zeile 151: 1224993 Ungültiger Maschinenbefehl "$binary_path" install ${TARGET:+"$TARGET"}
- Claude Code Segmentation fault
- [BUG] Segmentation Fault when starting Claude-Code in a VM in VirtualBox
- [BUG] Error: Claude Code process exited with code 3 when I tried to use the claude code plugin in visual studio code
- [BUG]
- Bun runtime SIGKILL's stdio MCP server process group after ~60s idle
- Claude Code 2.1.122 crashed with embedded Bun v1.3.14 segfault at address 0x38
- [BUG] claude crashes with Bun segfault on Windows 10 + Intel 13th Gen (i7-13700H)
- [Bug] Bun runtime segfault on Windows caused by astMC.dll (Hammock AssetView +) hook injection — triggered by image read operations
- [BUG] Bun segfault (SIGSEGV at 0x0) on exit - macOS Apple Silicon
- [BUG] Claude Code VS Extension - Claude Code process exited with code 3, Bun
- [BUG] Claude Chrome extension Computer Tool crashes Chrome — debugger detach + GetAIPageContent flooding + ChildFrameCrash
- v2.1.72 standalone Linux binary crashes with illegal instruction on Haswell (i7-4790K)
- Segfault crash after Windows sleep/wake with active session
- [BUG] SIGABRT error in VS Code with Claude extension
- [BUG] No minimum CPU requirements check
- [Bug] Segmentation Fault on Windows with Bun Runtime
- Recurring Bun segfault crashes (~3x/week) on Linux x64 AMD
- [Bug] Segmentation fault in Bun runtime during Claude Code execution
- [Bug] Cowork VM Kernel Panic in xt_net_init during bwrap Network Namespace Creation
- SIGABRT crash: native .node addon deleted from /tmp during runtime (v2.1.42)
- Segfault on Windows 11 Enterprise with Citrix — ctiuser.dll in crash stack
- Claude CLI core dumps (SIGSEGV/SIGABRT) during active sessions
- User-scoped MCP servers crash Claude Code on Windows (segfault)
- Segmentation fault crash on Windows x64 (Bun Canary v1.3.9-canary.51)
- System Crashes in Production: Process Explosion & Resource Exhaustion (Ubuntu 22.04, v2.1.30-2.1.32)
- [Bug] Print mode crashes with segfault on Windows; interactive mode fails on non-C: drives
- Windows: Bundled Bun 1.3.5 crashes with segmentation fault
- [BUG] - Bun ：1.3.5 - Claude Code ：2.1.22 - Bug：Segmentation fault at address 0xFFFFFFFFFFFFFFFF - Onset：Long time running（~40min）、memory peak 1.8GB
- [BUG] OAuth authentication not persisting in Docker container despite credentials file being saved
- Bun segfault during extended multi-agent workflow (Windows)
- Segfault crash on Windows: Bun v1.3.5 segmentation fault during long-running agent task
- [BUG] Bun crash
- [BUG] Segmentation fault when running multiple Claude Code instances in parallel
- [BUG] Segmentation fault on interactive startup on Synology NAS (React 19 + Ink incompatibility)
- Bun runtime segfault crash during long session
- [BUG] claude code crash error
- [Bug] Segmentation fault during resume command execution
- [BUG] crash
- Error: Claude Code process terminated by signal SIGABRT
- [Bug] Claude Code makes VSC crashing
- [BUG]
- [BUG] claude crashes when using @syntax pointing at an image file in CLAUDE.md
- [Bug] Claude Session Not Initializing Automatically in Extension
- [Bug] Persistent Memory and Model Configuration Hallucination Issues
- Segmentation Fault in Main Thread During Runtime
- JSON Parsing Error: Invalid Low Surrogate in Request Body
- iOS Simulator sidecar aborts on every frame render (SIGABRT in -[_MTLDevice recordBinaryArchiveUsage:])
- v2.1.243 segfaults before main() — bundled allocator interposes glibc free(), crashes in __newlocale (native install, Linux x86-64)
- Out-of-bounds read past end of 1 GiB mapping on CPUs without AVX/SSE4 (SIGSEGV, not SIGILL)
- Title: Bun runtime segfault crashes claude-vscode after long-running session (v2.1.229)
- [BUG] Bun-level crash during foreground subagent (Agent tool) dispatch — v2.1.224, Windows
- iOS Simulator panel crashes repeatedly with SIGABRT in Metal screen-capture path
- Claude Code crashes with SIGSEGV after ~19hr uptime with recurring caffeinate subprocess activity
- Injected grep wrapper (bundled ugrep) consumes 20+ GB RAM on bounded-repeat regex, hard-freezes machine
- [BUG] Anti-cheat driver crashes bundled Bun runtime; surfaced only as "process exited with code 3"
- grep shim (embedded ugrep 7.5.0) allocates unbounded memory on double-bounded-repeat BRE patterns — can OOM-kill the host