You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenCode 1.17.10 crashes on startup with Bun segmentation fault (Windows) #33779
Environment
OS: Windows 11 (10.0.26200.8655)
OpenCode: 1.17.10
Bun: 1.3.11
Bun Path: C:\Users\User.bun\bin\bun.exe
Description
OpenCode crashes immediately on startup with a Bun segmentation fault.
The crash occurs even in a completely empty directory and is not related to any specific project.
Steps to Reproduce
Open Command Prompt.
Create an empty directory:
mkdir C:\empty-test
cd C:\empty-test
Run:
opencode
OpenCode crashes with a Bun segmentation fault.
Expected Behavior
OpenCode should start normally.
Actual Behavior
Startup crashes with:
panic(main thread): Segmentation fault
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Additional Information
bun repl works correctly.
opencode --help works correctly.
Crash occurs in both project folders and empty folders.
Issue started after upgrading to OpenCode 1.17.10.
Previous version (1.17.9) worked correctly on the same machine.
Diagnostic Results
bun --version
1.3.11
opencode --version
1.17.10
where bun
C:\Users\User.bun\bin\bun.exe
Notes
This appears to be a startup/runtime regression introduced in 1.17.10 on Windows, since:
Bun itself is functional (bun repl works).
OpenCode CLI commands such as --help work.
Only starting the TUI causes the crash.
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Reacted by KhanhDz, Rizky Putra Ednar, CristianQ27, C, 黎毅麟, SR90MJ, Chansa Garcia, Jirayuth Porka, Mindless, xcwen6 and 3 more
Activity
github-actions commentedon Jun 25, 2026
This issue might be a duplicate of existing issues. Please check:
c0dehvb commentedon Jun 25, 2026
+1
Chaser-X commentedon Jun 25, 2026
+1
zidanindratama commentedon Jun 25, 2026
+1 please fix this asap.
1107186916 commentedon Jun 25, 2026
+1
503203440 commentedon Jun 25, 2026
+1
LOYINuts commentedon Jun 25, 2026
same