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
I encountered the same error in multiple versions. It still exists in the latest version (1.1.36). There is information that upgrading the bun to 1.3.6 can solve it.
CPU lacks AVX support. Please consider upgrading to a newer CPU.
panic(thread 41960): Segmentation fault at address 0x4A2B21E0160
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:
panic(thread 38780): Segmentation fault at address 0x0 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/ea11e86cebmzGz+3/9/DA2AA
The bun crashes are bun issues, we are in the works of moving off of bun to node since crashes are too pervasive.
Without making this decision for you, I think we were hopping for this. Absolutely a bun issue. I thought it might just be a new release OpenCode needed to move to with fixes, but over last few weeks and searching existing issues, it does seem pervasive.
If there is already an option to run OpenCode with node instead of bun, please let me know. (bun seems to be part of windows binary and installing with npm did not help).
I tried using the npm install path directly, but unfortunately it did not avoid Bun for me.
npm install -g opencode-ai still appeared to install/invoke the bundled .opencode standalone executable, and the crash output still showed:
Bun v1.3.x ... [StandaloneExecutable]
So my read is that npm installs the CLI package, but the actual OpenCode runtime is still the Bun-compiled binary, at least in the current release. This matches other reports where the npm/binary package still includes a Bun standalone executable, and OpenCode’s plugin docs also note that npm plugins are installed using Bun and cached under ~/.cache/opencode/node_modules/.
So unless there is a hidden flag or newer branch that runs OpenCode fully under Node, I do not think npm is currently a true Node-only workaround.
The same problem has been occurring on my computer for a very long time. When will the official team address this issue and resolve it?
Suggestion: You can directly enable opencode through node instead of bun.
In the long term, it is recommended to replace bun.
Activity
github-actions commentedon Jan 16, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
andrey-pavlenko commentedon Jan 16, 2026
The same problem occurs in Arch Linux. Opencode was installed from the AUR https://aur.archlinux.org/packages/opencode-bin.
n-pll commentedon Jan 26, 2026
I encountered the same error in multiple versions. It still exists in the latest version (1.1.36). There is information that upgrading the bun to 1.3.6 can solve it.
Bun v1.3.5 (1e86cebd) Windows x64 (baseline)
Windows v.win10_rs5 Z.AI Coding Plan /E:\project\oh-my-opencode:dev
Args: "C:\Users\aiguo\AppData\Roaming\npm\node_modules\opencode-ai\node_modules\opencode-windows-x64\bin\opencode.exe" "--user-agent=opencode/1.1.36" "--use-system-ca " "--"▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Features: Bun.stderr(4) Bun.stdin(4) Bun.stdout(4) abort_signal(2) bunfig fetch(303) jsc no_avx2 no_avx shell(698) spawn(385) standalone_executable transpiler_cache(4) tsconfig(4) workers_spawned(2) napi_module_register process_dlopen ode 1.1.36
Builtins: "bun:ffi" "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:console" "node:constants" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:process" "node:querystring" "node:readline" "node:readline/promises" "node:stream" "node:string_decoder" "node:timers" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:worker_threads" "undici" "node:v8" "node:http2" "node:diagnostics_channel" "node:dgram"
Elapsed: 1529861ms | User: 17468ms | Sys: 6421ms
RSS: 1.26GB | Peak: 1.26GB | Commit: 1.63GB | Faults: 632771 | Machine: 34.19GB
CPU lacks AVX support. Please consider upgrading to a newer CPU.
panic(thread 41960): Segmentation fault at address 0x4A2B21E0160
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/ea11e86cebmzGz63/9f_+wlwekhlwe4/i3nB06twzB063vzB6ivtzBsputzB8l35uB80tiwB+itiwBuisiwB0vm3nB89/7qBy8/8e___A2kqChq/n8tC
erskingardner commentedon Jan 29, 2026
Same on macos too with opencode v1.1.42
mykola-dev commentedon Feb 3, 2026
panic(thread 38780): Segmentation fault at address 0x0 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/ea11e86cebmzGz+3/9/DA2AA
win10, win terminal
ouchihao commentedon Feb 6, 2026
I also encountered the same problem. Even though I used bun 1.3.8, I still couldn't solve it.
natanim-kemal commentedon Feb 6, 2026
Same here
============================================================
Bun v1.3.5 (1e86cebd) Windows x64
Windows v.win11_dt
CPU: sse42 avx avx2
Args: "C:\Users\Hp\AppData\Roaming\npm\node_modules\opencode-ai\node_modules\opencode-windows-x64\bin\opencode.exe"
Elapsed: 3ms | User: 15ms | Sys: 0ms
RSS: 17.41MB | Peak: 17.41MB | Commit: 55.55MB | Faults: 4412
panic(main thread): Segmentation fault at address 0x7FF71BFD7B97
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/w_11e86cebAAoj7xFuvbgjMopvizDCYKERNEL32.DLLut0LCSntdll.dll4gijBA2u//Bu591/b
zhenbiao-l commentedon Feb 9, 2026
I also encountered the same problem. Even though I used bun 1.3.8, I still couldn't solve it.
WangNingkai commentedon Feb 11, 2026
23 remaining items
christian-taillon commentedon Apr 24, 2026
Without making this decision for you, I think we were hopping for this. Absolutely a bun issue. I thought it might just be a new release OpenCode needed to move to with fixes, but over last few weeks and searching existing issues, it does seem pervasive.
Thank you for the update.
stefaneidelloth commentedon May 5, 2026
If there is already an option to run OpenCode with node instead of bun, please let me know. (bun seems to be part of windows binary and installing with npm did not help).
christian-taillon commentedon May 6, 2026
I tried using the npm install path directly, but unfortunately it did not avoid Bun for me.
npm install -g opencode-aistill appeared to install/invoke the bundled.opencodestandalone executable, and the crash output still showed:So my read is that npm installs the CLI package, but the actual OpenCode runtime is still the Bun-compiled binary, at least in the current release. This matches other reports where the npm/binary package still includes a Bun standalone executable, and OpenCode’s plugin docs also note that npm plugins are installed using Bun and cached under
~/.cache/opencode/node_modules/.So unless there is a hidden flag or newer branch that runs OpenCode fully under Node, I do not think npm is currently a true Node-only workaround.
Mte90 commentedon May 6, 2026
It is happening a lot with the latest version, on discord we are discussing about it https://discord.com/channels/1391832426048651334/1501486014101717102
It happens on 1.14.39
Mte90 commentedon May 6, 2026
In my case the report is https://bun.report/1.3.13/Ba1bf2e2cem5Gz/339/D4vyi7E+inQwgqvmDA2AI
There is a way to use nodejs in the meantime?
Mte90 commentedon May 6, 2026
Similar issue #24148
Mte90 commentedon May 6, 2026
I believe that oven-sh/bun#29464 is the culprit
Mte90 commentedon May 7, 2026
I can confirm that downgrading to 1.14.33 works, just remember to disable the autoupdate.
J4n3kk commentedon May 8, 2026
It was crashing on the 1.14.33, seems like bun fix is waiting to be approved -> oven-sh/bun#30349
Electricitysheep commentedon May 11, 2026
复现报告:v1.14.48 更新后 Bun 再次崩溃(反复出现的老问题)
环境
npm install -g opencode-ai问题描述
每次 OpenCode 更新版本后,Bun 几乎必然在第一次启动时崩溃。从 v1.14.39 开始这个问题就反复出现,v1.14.48 再次复现。这不是第一次发生——几乎每次大版本更新都会触发。
复现步骤
npm install -g opencode-ai或等待自动更新到新版本opencodeSegmentation fault或panic(main thread)oh no: Bun has crashed. This indicates a bug in Bun, not your code.关键观察
与其他 Issue 的关系
这个问题已经被多次报告(#8785, #14724, #14941, #15056, #15283, #24075),但每次版本更新都再次出现,说明Bun 运行时版本的兼容性并不是一次性解决的。
建议
既然 @rekram1-node 在 #8785 中已经提到 "we are in the works of moving off of bun to node since crashes are too pervasive",希望这个迁移工作能尽快完成。在此之前:
附:oven-sh/bun#30349 可能是相关的 Bun 修复等待合入。
Stven-ben commentedon May 12, 2026
The same problem has been occurring on my computer for a very long time. When will the official team address this issue and resolve it?
Suggestion: You can directly enable opencode through node instead of bun.
In the long term, it is recommended to replace bun.
avonyu commentedon Jun 25, 2026
It means that we need using npm/pnpm to install opencode instead of bun?