Title: Bun runtime segfault crashes claude-vscode after long-running session (v2.1.229)

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?

Title: Bun runtime segfault crashes claude-vscode after long-running session (v2.1.229)

Environment:

• claude-code version: 2.1.229 (cc_entrypoint=claude-vscode)
• Bun v1.4.0 (8bb8d04c4)
• Windows 11 x64 (build 10.26200), CPU features: sse42 avx avx2 avx512

What happened:
After a long-running session (elapsed ~12,505,445ms / ~3.5h; RSS 0.49GB, peak 0.54GB), the bundled Bun runtime segfaulted on the main thread and killed the CLI process:

panic(main thread): Segmentation fault at address 0x1DA184D4020
oh no: Bun has crashed.

Bun's own crash reporter produced this report link:
https://bun.report/1.4.0/w_18bb8d04mgggkIuhogC6giubiwi9+Bsk14tCotlj6B2hoi6B666u6Bup859Bk4yk6Byyj+a84lh/BoxusSosojO2o/h7DyovhTqts2Wwxh+5DCYKERNEL32.DLLurmLCSntdll.dll422qBA20dgig1pY

Claude Code process exited with code 3. No repo/file corruption resulted - verified working tree and git reflog were clean afterward.

Impact: mid-session crash, user had to reload the VS Code window to recover.

What Should Happen?

it should no crash

Error Messages/Logs

Steps to Reproduce

1 was a onetime

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.229

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_