[BUG] Segmentation fault at address

Open 💬 9 comments Opened Apr 21, 2026 by serkanz

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

  1. Create a code repo with some basic code.
  2. open claude code cli under that repo
  3. 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_

View original on GitHub ↗

This issue has 9 comments on GitHub. Read the full discussion on GitHub ↗