Segmentation fault crash on Windows x64 (Bun Canary v1.3.9-canary.51)

Resolved 💬 3 comments Opened Feb 9, 2026 by rrs1979 Closed Feb 13, 2026

Description

Claude Code crashes with a segmentation fault after ~5.75 minutes of usage on Windows 11 x64.

Crash Log

Bun Canary v1.3.9-canary.51 (d5628db2) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2
Args: "C:\Users\roman\.local\bin\claude.exe" "--allow-dangerously-skip-permissions"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) abort_signal(39) fetch(197) jsc spawn(321) standalone_executable process_dlopen yaml_parse(49)
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "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:querystring" "node:stream" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:zlib" "node:worker_threads" "undici" "ws" "node-fetch" "node:http2"
Elapsed: 345347ms | User: 31140ms | Sys: 7171ms
RSS: 0.68GB | Peak: 0.75GB | Commit: 0.95GB | Faults: 731663 | Machine: 34.06GB

panic(main thread): Segmentation fault at address 0xFFFFFFFFFFFFFFFF
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

Bun crash report URL

https://bun.report/1.3.9/e_2d5628dbmgkgEuhogCgm+2W88outB4s+mqC49uiqC6ssiqCy7sqXozg0U23wN2/tgUm17jOimsjOw0vxvDCYKERNEL32.DLLut0LCSntdll.dll4zijBA2DD

Environment

  • Claude Code version: 2.1.37
  • OS: Windows 11 x64
  • RAM: 34 GB
  • Bun version (bundled): Canary v1.3.9-canary.51
  • CPU features: SSE4.2, AVX, AVX2

Notes

  • The segfault address 0xFFFFFFFFFFFFFFFF (-1) suggests a null/invalid pointer dereference
  • Memory usage at crash time was moderate (0.68GB RSS / 0.75GB peak) — not an OOM situation
  • The crash occurred after ~345 seconds of normal operation
  • The bundled Bun runtime is a canary build — consider shipping stable Bun releases to reduce crashes like this

View original on GitHub ↗

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