[BUG]
Status Open
Reported on v2.1.139
Maintainer reply None cached
Activity 0 comments · opened Aug 26, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
What's wrong?
Claude Code segfaults immediately on startup (claude, claude --version) across
multiple versions (tested 2.1.139, 2.1.200, 2.1.246 — all segfault identically).
This looks like the same class of bug as #76241, but on a newer glibc than
previously reported there.
Environment
- OS: Arch Linux (rolling release, fully updated)
- glibc: 2.44 (
ldd --version) - Kernel/arch: x86_64
- CPU: AVX + AVX2 present (confirmed via /proc/cpuinfo)
- Node: v22.22.2 installed separately (irrelevant — Claude Code bundles its own Bun runtime)
- Install method: npm (
npm install -g @anthropic-ai/claude-code), also tried with
--allow-scripts to ensure postinstall ran
Related
https://github.com/anthropics/claude-code/issues/76241
What Should Happen?
Expected behavior
Claude Code should run normally, or at minimum fail with a readable error instead
of a raw SIGSEGV, on systems with a newer glibc than the bundled Bun binary expects.
Error Messages/Logs
Steps to Reproduce
Steps to reproduce
npm install -g @anthropic-ai/claude-code- Run
claude - Immediate
SIGSEGV (Address boundary error), no output printed
What I've ruled out
- Not an install-scripts/postinstall issue (reproduces with scripts explicitly allowed)
- Not a Node version/arch mismatch (system Node runs fine independently)
- Not an AVX-support issue (CPU has AVX2; this isn't the "CPU lacks AVX" crash)
- Not version-specific — segfaults on 2.1.139, 2.1.200, and latest (2.1.246)
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.246
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
Other
Additional Information
_No response_