Bun segfault crash (0xFFFFFFFFFFFFFFFF) on Windows during normal usage

Resolved 💬 4 comments Opened Feb 26, 2026 by jiaoshi888 Closed Mar 26, 2026

Bug Description

Claude Code crashes with a Bun segmentation fault during normal usage on Windows.

Environment

  • Claude Code: v2.1.44
  • Model: Opus 4.6 (Claude Max)
  • Bun: Canary v1.3.9-canary.62 (6d2fefba) Windows x64 (baseline)
  • OS: Windows 10 (win10_ni)
  • CPU: sse42 avx avx2
  • Machine RAM: 68.53GB

Error Output

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

Memory Stats at Crash

  • RSS: 0.80GB | Peak: 0.86GB | Commit: 1.19GB
  • Faults: 322751
  • Elapsed: 71107ms (~71 seconds into the session)

Steps to Reproduce

  1. Launch Claude Code on Windows (claude command)
  2. Start a normal conversation session
  3. Crash occurs ~71 seconds into the session with segfault

Bun Crash Report Link

The crash generated a Bun report link:

https://bun.report/1.3.9/e_26d2fefbmgkgEuhogDgm+2W88outB4s+mqCU9uiqC6ssiqCy7sqXozg0U23wN2/tgUm17jOimsjOw0vxvDCYKERNEL32.DLLo35FCSntdll.dllipmTA2DD

Additional Context

  • This happened at session startup, approximately 71 seconds after launch
  • The working directory was a git repository (E:\Lyricist)
  • Permission mode was set to "don't ask on"

View original on GitHub ↗

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