Skip to content

Bun has crashed #11886

Closed as duplicate
Closed as duplicate

Description

@huahua-byte

Description

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

To send a redacted crash report to Bun's team,
please file a GitHub issue using the link below:

https://bun.report/1.3.5/ea11e86cebEugogCCcLHShield64.dll4oyhCCcLHShield64.dlly2xhCCcLHShield64.dllugoOCcLHShield64.dllmhjTCcLHShield64.dllwgVCcLHShield64.dlls45tCCcLHShield64.dllizxfCcLHShield64.dll66mfCcLHShield64.dlloyyyB+52nuBu32mgB61/8f__0shkwCA2spBt1683+C

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Windows v.win11_dt

Terminal

No response

Activity

  1. added
    perfIndicates a performance issue or need for optimization
    on Feb 3, 2026
  2. github-actions commented on Feb 3, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    All of these are Windows-related segmentation faults with Bun v1.3.5, which appears to be a known issue affecting multiple features. Feel free to ignore if your specific case differs from these.

  3. rekram1-node commented on Feb 3, 2026

    @rekram1-node
    Contributor

    bun bug, tho they have apparently fixed some of these in latest releases, we will upgrade bun soon

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