Bun Segmentation Fault at address 0xffffffffffffffff #9250

Open
opened 2026-02-16 18:12:00 -05:00 by yindo · 4 comments
Owner

Originally created by @kznr02 on GitHub (Feb 13, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

Lauch a session for a while, bun crashed with seg fault log.

Bun crash log link Here

Image

Plugins

oh-my-opencode

OpenCode version

1.1.65

Steps to reproduce

  1. type my requirement.
  2. send to agent
  3. for seconds, it's crashed without any sign.

Screenshot and/or share link

Session Link: https://opncd.ai/share/ya5NX55s

The last page of session:

Image

Operating System

Windows 11

Terminal

Windows Terminal

Originally created by @kznr02 on GitHub (Feb 13, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description Lauch a session for a while, bun crashed with seg fault log. Bun crash log link [Here](https://bun.report/1.3.9/wa1cf6cdbbm2Gz+3/9/Di4mwIw00yEszqkEmoy1D+ry1wBqwgxwB64+wwB6mt+d2ozypBip39dCYKERNEL32.DLLut0LCSntdll.dll4zijBA2DD) <img width="1475" height="721" alt="Image" src="https://github.com/user-attachments/assets/a6eb64e9-e8c6-426a-beda-f421be43ebbf" /> ### Plugins oh-my-opencode ### OpenCode version 1.1.65 ### Steps to reproduce 1. type my requirement. 2. send to agent 3. for seconds, it's crashed without any sign. ### Screenshot and/or share link Session Link: https://opncd.ai/share/ya5NX55s The last page of session: <img width="2560" height="1380" alt="Image" src="https://github.com/user-attachments/assets/7e102b09-c4d0-462e-8022-3afe41ea328c" /> ### Operating System Windows 11 ### Terminal Windows Terminal
yindo added the windowsbugperf labels 2026-02-16 18:12:00 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 13, 2026):

This issue might be a duplicate of existing Windows/Bun segmentation fault reports. Please check if your issue is related to:

  • #13282: OpenCode 1.1.59 crashes immediately on chat (Bun AVX crash)
  • #8785: Bun has crashed (Windows segmentation fault)
  • #12763: OpenCode v1.1.53 randomly crashes during usage on Windows
  • #11824: Windows binary compiled with Bun 1.3.5, causing LSP crashes

These issues describe similar Bun segmentation faults on Windows systems. If your issue is the same or very similar, please add your details (OS version, terminal, crash logs, steps to reproduce) to one of the existing issues rather than creating a new one. This helps consolidate reports and makes it easier for maintainers to track and resolve the root cause.

If your issue has unique characteristics not covered by the above, please describe what makes it different.

@github-actions[bot] commented on GitHub (Feb 13, 2026): This issue might be a duplicate of existing Windows/Bun segmentation fault reports. Please check if your issue is related to: - #13282: OpenCode 1.1.59 crashes immediately on chat (Bun AVX crash) - #8785: Bun has crashed (Windows segmentation fault) - #12763: OpenCode v1.1.53 randomly crashes during usage on Windows - #11824: Windows binary compiled with Bun 1.3.5, causing LSP crashes These issues describe similar Bun segmentation faults on Windows systems. If your issue is the same or very similar, please add your details (OS version, terminal, crash logs, steps to reproduce) to one of the existing issues rather than creating a new one. This helps consolidate reports and makes it easier for maintainers to track and resolve the root cause. If your issue has unique characteristics not covered by the above, please describe what makes it different.
Author
Owner

@danielabelski commented on GitHub (Feb 16, 2026):

I’m seeing the same Bun crash pattern on Windows, but in OpenCode Desktop’s spawned local server (sidecar).

Environment:

Windows 11 x64
OpenCode Desktop spawns: opencode-cli.exe
opencode-cli.exe --version: 1.2.5
Crash output shows: Bun v1.3.9 (cf6cdbbb) Windows x64 (baseline)
Symptoms:

Desktop starts the local sidecar server normally (Server ready, CLI health check OK).
After running for a while, the sidecar crashes:
panic(main thread): Segmentation fault ...
followed by a bun.report link
then Sidecar terminated code=Some(3)
Desktop then loses the local server connection (Received Exit, Killed server).
Desktop logs:

Example crash logs:

panic(main thread): Segmentation fault ...
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Sidecar terminated code=Some(3) Then Desktop reports exit/kill of the server.

https://bun.report/1.3.9/ea1cf6cdbbmnGz+339/DoqpkwB0w6/vBu4k0Hw6vyH0wlwG2kkrpB8r94FmubqiMwwy3uDCYKERNEL32.DLLut0LCSntdll.dll4gijBA263CwqqgrE
https://bun.report/1.3.9/ea1cf6cdbbmnGz+339/Dwl/jwBs3u+tBm+8+tBi2hkwBqt8/vB6n6/vBu4k0Hw6vyH0wlwG2kkrpB8r94FmubqiMwwy3uDCYKERNEL32.DLLut0LCSntdll.dll4gijBA2muBhu+jypC

@danielabelski commented on GitHub (Feb 16, 2026): I’m seeing the same Bun crash pattern on Windows, but in OpenCode Desktop’s spawned local server (sidecar). Environment: Windows 11 x64 OpenCode Desktop spawns: opencode-cli.exe opencode-cli.exe --version: 1.2.5 Crash output shows: Bun v1.3.9 (cf6cdbbb) Windows x64 (baseline) Symptoms: Desktop starts the local sidecar server normally (Server ready, CLI health check OK). After running for a while, the sidecar crashes: panic(main thread): Segmentation fault ... followed by a bun.report link then Sidecar terminated code=Some(3) Desktop then loses the local server connection (Received Exit, Killed server). Desktop logs: Example crash logs: ``` panic(main thread): Segmentation fault ... oh no: Bun has crashed. This indicates a bug in Bun, not your code. Sidecar terminated code=Some(3) Then Desktop reports exit/kill of the server. ``` https://bun.report/1.3.9/ea1cf6cdbbmnGz+339/DoqpkwB0w6/vBu4k0Hw6vyH0wlwG2kkrpB8r94FmubqiMwwy3uDCYKERNEL32.DLLut0LCSntdll.dll4gijBA263CwqqgrE https://bun.report/1.3.9/ea1cf6cdbbmnGz+339/Dwl/jwBs3u+tBm+8+tBi2hkwBqt8/vB6n6/vBu4k0Hw6vyH0wlwG2kkrpB8r94FmubqiMwwy3uDCYKERNEL32.DLLut0LCSntdll.dll4gijBA2muBhu+jypC
Author
Owner

@kznr02 commented on GitHub (Feb 16, 2026):

I’m seeing the same Bun crash pattern on Windows, but in OpenCode Desktop’s spawned local server (sidecar).

Environment:

Windows 11 x64 OpenCode Desktop spawns: opencode-cli.exe opencode-cli.exe --version: 1.2.5 Crash output shows: Bun v1.3.9 (cf6cdbbb) Windows x64 (baseline) Symptoms:

Desktop starts the local sidecar server normally (Server ready, CLI health check OK). After running for a while, the sidecar crashes: panic(main thread): Segmentation fault ... followed by a bun.report link then Sidecar terminated code=Some(3) Desktop then loses the local server connection (Received Exit, Killed server). Desktop logs:

Example crash logs:

panic(main thread): Segmentation fault ...
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Sidecar terminated code=Some(3) Then Desktop reports exit/kill of the server.

https://bun.report/1.3.9/ea1cf6cdbbmnGz+339/DoqpkwB0w6/vBu4k0Hw6vyH0wlwG2kkrpB8r94FmubqiMwwy3uDCYKERNEL32.DLLut0LCSntdll.dll4gijBA263CwqqgrE https://bun.report/1.3.9/ea1cf6cdbbmnGz+339/Dwl/jwBs3u+tBm+8+tBi2hkwBqt8/vB6n6/vBu4k0Hw6vyH0wlwG2kkrpB8r94FmubqiMwwy3uDCYKERNEL32.DLLut0LCSntdll.dll4gijBA2muBhu+jypC

Bun is soooooo unstable, my computer is AMD ZEN4 CPU, opencode works good on my Intel PC.
Now I’m doubt if it corresponds to CPU Platform.

@kznr02 commented on GitHub (Feb 16, 2026): > I’m seeing the same Bun crash pattern on Windows, but in OpenCode Desktop’s spawned local server (sidecar). > > Environment: > > Windows 11 x64 OpenCode Desktop spawns: opencode-cli.exe opencode-cli.exe --version: 1.2.5 Crash output shows: Bun v1.3.9 (cf6cdbbb) Windows x64 (baseline) Symptoms: > > Desktop starts the local sidecar server normally (Server ready, CLI health check OK). After running for a while, the sidecar crashes: panic(main thread): Segmentation fault ... followed by a bun.report link then Sidecar terminated code=Some(3) Desktop then loses the local server connection (Received Exit, Killed server). Desktop logs: > > Example crash logs: > > ``` > panic(main thread): Segmentation fault ... > oh no: Bun has crashed. This indicates a bug in Bun, not your code. > Sidecar terminated code=Some(3) Then Desktop reports exit/kill of the server. > ``` > > https://bun.report/1.3.9/ea1cf6cdbbmnGz+339/DoqpkwB0w6/vBu4k0Hw6vyH0wlwG2kkrpB8r94FmubqiMwwy3uDCYKERNEL32.DLLut0LCSntdll.dll4gijBA263CwqqgrE https://bun.report/1.3.9/ea1cf6cdbbmnGz+339/Dwl/jwBs3u+tBm+8+tBi2hkwBqt8/vB6n6/vBu4k0Hw6vyH0wlwG2kkrpB8r94FmubqiMwwy3uDCYKERNEL32.DLLut0LCSntdll.dll4gijBA2muBhu+jypC Bun is soooooo unstable, my computer is AMD ZEN4 CPU, opencode works good on my Intel PC. Now I’m doubt if it corresponds to CPU Platform.
Author
Owner

@danielabelski commented on GitHub (Feb 16, 2026):

Bun is soooooo unstable, my computer is AMD ZEN4 CPU, opencode works good on my Intel PC. Now I’m doubt if it corresponds to CPU Platform.

I see this on intell ultra 7 155h laptop

@danielabelski commented on GitHub (Feb 16, 2026): > Bun is soooooo unstable, my computer is AMD ZEN4 CPU, opencode works good on my Intel PC. Now I’m doubt if it corresponds to CPU Platform. I see this on intell ultra 7 155h laptop
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9250