[BUG] Segmentation fault at address
Status Open
Reported on v2.1.116
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 11 comments · opened Apr 21, 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?
On a repo (no matter it's a git repo or not) when I run /init, after 30~seconds claude code cli (2.1.116 or 2.1.114) crashes on a Windows 10 OS with Node v24.15.0 (older node versions had the same result). Below is the error message :
Bun v1.3.13 (743d2a40) Windows x64 (baseline)
Windows v.win10_cu
CPU: sse42 avx avx2
Args: "C:\Users\XXXXX\node\node_modules\@anthropic-ai\claude-code\bin\claude.exe"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) abort_signal(13) fetch(26) http_client_proxy(22) jsc spawn(19) standalone_executable yaml_parse(2) claude_code
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:stream" "node:stream/consumers" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:vm" "node:zlib" "undici" "ws" "node:http2"
Elapsed: 33310ms | User: 6046ms | Sys: 1687ms
RSS: 0.56GB | Peak: 0.58GB | Commit: 0.76GB | Faults: 206490 | Machine: 68.63GB
panic(thread 18196): Segmentation fault at address 0xCD
panic: Segmentation fault at address 0xC8
panicked during a panic. Aborting.Same happens for claude desktop latest version also.
2.1.112 working fine. When I run wsl on the same machine it also works. I suspect it's an OS specific issue.
What Should Happen?
Claude Code executes commands as expected.
Error Messages/Logs
Bun v1.3.13 (743d2a40) Windows x64 (baseline)
Windows v.win10_cu
CPU: sse42 avx avx2
Args: "C:\Users\XXXXX\node\node_modules\@anthropic-ai\claude-code\bin\claude.exe"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) abort_signal(13) fetch(26) http_client_proxy(22) jsc spawn(19) standalone_executable yaml_parse(2) claude_code
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:stream" "node:stream/consumers" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:vm" "node:zlib" "undici" "ws" "node:http2"
Elapsed: 33310ms | User: 6046ms | Sys: 1687ms
RSS: 0.56GB | Peak: 0.58GB | Commit: 0.76GB | Faults: 206490 | Machine: 68.63GB
panic(thread 18196): Segmentation fault at address 0xCD
panic: Segmentation fault at address 0xC8
panicked during a panic. Aborting.Steps to Reproduce
- Create a code repo with some basic code.
- open claude code cli under that repo
- run /init
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.112
Claude Code Version
2.1.116
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
Update
Crash occurs even if I don't execute any command and wait at claude command prompt. and it doesn't log any error related log (it logs other stuff so --debug is working) to .claude/debug folder.
_No response_
11 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
bugs you listed are not duplicate of this bug. 2.1.112 is working fine however 2.1.114 and 2.1.116 not.
issue still exists on 2.1.123. Claude Desktop 1.5354.0 has the same problem. any comment ?
related to #50640
Affected environment:
Crash output:
Reproduction: 100% reproducible on every launch, both as regular user and as Administrator.
Workarounds attempted (all failed):
node cli-wrapper.cjs(the wrapper also spawns the .exe)BUN_JSC_useWebAssemblySIMD=0and other JSC env vars — all returned "invalid JSC environment variable"Notes: The crash address
0xCC/0xC8matches exactly the pattern in this issue. The binary runs inbaselinemode despite the CPU supporting AVX512, which may indicate incorrect CPU feature detection on Intel 11th Gen Tiger Lake.Please consider shipping a Windows build that explicitly disables AVX512, or providing a fallback execution path via Node.js for affected hardware.
related to #58586
please provide a fix for this asap. we cannot use our subscription as we expect.
@serkanz Only successful workaround is to run wsl and install claude there and use WSL to access your windows directories. I have tried to use alternative method of installation via npm instead of the cmd/powershell script but it is still failing with the same error.
any update on this?
Hello, any update on this? I am facing this too on v2.1.215 of claude code with v1.4.0 of bun, it's pretty frustrating!
Workaround found: disable the JSC FTL JIT tier via
BUN_JSC_useFTLJIT=0Environment: Windows 10/11 (10.26200), x64, native install at
~/.local/bin/claude.exe. Crash reproduced on every launch (evenclaude -p "ok"), ~5s after start, on CLI 2.1.218/2.1.219/2.1.220 (Bun 1.4.0f6d0fcd, baseline build) and on 2.1.154 (Bun 1.3.14). Segfault address 0x3C.Diagnosis:
--settings '{"hooks": {}}'in an empty dir).cli.jsunder Node 24) runs fine, as does the Linux build under WSL2 — so this is specific to the bundled Bun runtime on this machine.BUN_JSC_useFTLJIT=0makes the native Windows binary run reliably (verified 3/3 launches withclaude -p).BUN_JSC_useJIT=0(all JIT tiers off) also works; FTL-only is the minimal tier to disable.Deployment:
setx BUN_JSC_useFTLJIT 0persists it for the user; new terminals pick it up.This points the root cause at the FTL JIT in Bun's Windows x64 baseline build on affected machines rather than Claude Code app code. Hope this helps narrow it down.