Segmentation fault (SIGSEGV / SIGABRT) — page 3

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.

  1. Record the Claude Code version and the first stack frame before restarting.
  2. Try a fresh session with the same minimal input to distinguish corrupted state from a repeatable crash.
  3. 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.

0 20 40 59 79 2025-042025-092026-032026-08
2025-04 — First reports2026-08 — Peak backlog (79 open)

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:

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 201–289

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. AbortError: the operation was aborted

    2,101 issues
  2. SyntaxError: Unexpected token

    698 issues
  3. Killed: 9 (SIGKILL / OOM killer)

    339 issues
  4. TypeError: Cannot read properties of undefined

    194 issues
  5. JavaScript heap out of memory

    142 issues
  6. Unhandled promise rejection

    59 issues