Skip to content

Bun Segmentation Fault at address 0xffffffffffffffff #13468

Closed
Closed
Bun Segmentation Fault at address 0xffffffffffffffff#13468
Assignees
rekram1-node
Labels
bugSomething isn't workingperfIndicates a performance issue or need for optimizationwindows

Description

@kznr02
kznr02
opened on Feb 13, 2026

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

Activity

  1. kznr02
    added
    bugSomething isn't working
    on Feb 13, 2026
  2. github-actions
    assigned
    rekram1-node
    on Feb 13, 2026
  3. github-actions
    added
    perfIndicates a performance issue or need for optimization
    windows
    on Feb 13, 2026

  4. github-actions commented on Feb 13, 2026

    @github-actions
    github-actionsBot
    on Feb 13, 2026 – with GitHub Actions
    Contributor

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

    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.

  5. danielabelski commented on Feb 16, 2026

    @danielabelski
    danielabelski
    on 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

  6. kznr02 commented on Feb 16, 2026

    @kznr02
    kznr02
    on Feb 16, 2026
    Author

    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.

  7. danielabelski commented on Feb 16, 2026

    @danielabelski
    danielabelski
    on 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

  8. Hoshino-Yumetsuki commented on Feb 18, 2026

    @Hoshino-Yumetsuki
    Hoshino-Yumetsuki
    on Feb 18, 2026

    I encountered the same situation today; my CPU is also AMD.

  9. IvRogoz commented on Feb 18, 2026

    @IvRogoz
    IvRogoz
    on Feb 18, 2026

    Here to

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

    doing a

    npm install -g opencode-ai@latest

    solved the issue for me.

  10. kznr02 commented on Feb 18, 2026

    @kznr02
    kznr02
    on Feb 18, 2026
    Author

    Here to

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

    doing a

    npm install -g opencode-ai@latest

    solved the issue for me.

    I’ve tried to reinstall opencode many times, still exists.
    I am not sure if I uninstall opencode completely.

  11. Hoshino-Yumetsuki commented on Feb 18, 2026

    @Hoshino-Yumetsuki
    Hoshino-Yumetsuki
    on Feb 18, 2026

    Here to
    panic(main thread): Segmentation fault at address 0x7FF74898795D oh no: Bun has crashed. This indicates a bug in Bun, not your code.
    doing a
    npm install -g opencode-ai@latest
    solved the issue for me.

    I’ve tried to reinstall opencode many times, still exists. I am not sure if I uninstall opencode completely.

    This dont seem to have anything to do with opencode itself and i think the crash issue is mainly caused by bun. I encountered this error so many times in one day that I now have to stop using opencode.

  12. killper commented on Feb 26, 2026

    @killper
    killper
    on Feb 26, 2026

    Here to

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

    doing a

    npm install -g opencode-ai@latest

    solved the issue for me.

    also works for me!

  13. kznr02 commented on Mar 8, 2026

    @kznr02
    kznr02
    on Mar 8, 2026
    Author

    It's been solved just upgrade to 1.2.20, seems a lot of bun api was replaced and the memory leak problem is also swipped, great work!

  14. kznr02
    closed this as completedon Mar 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingperfIndicates a performance issue or need for optimizationwindows

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions