Windows: embedded Bun 1.3.14 predates oven-sh/bun#35083 — opencode.exe segfaults whenever nProtect GameGuard (Helldivers 2) is running #44513

Activity

1. github-actions

   assigned

   Hona

   on Aug 23, 2026
2. github-actions commented on Aug 23, 2026

   

   github-actionsbot

   on Aug 23, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • OpenCode v1.17.10 crashes with Bun segmentation fault on Windows; v1.17.9 appears stable #33742: Windows Bun segfault with the same embedded Bun v1.3.14 runtime — overlapping root cause (outdated bundled Bun on Windows), though the trigger differs
   • Stack overflow via recursive exception dispatch in bundled Bun on every outbound fetch (Windows 11, v1.18.4 and v1.18.11) #40482: Recursive exception dispatch crash in bundled Bun on Windows fetch paths — also caused by the VEH/exception-handler behavior in the embedded Bun runtime

   If the fix in oven-sh/bun#35083 (Bun 1.4.0) resolves the underlying exception-handler issue, it may address those reports as well. Cross-linking for maintainer visibility.
3. nyecov commented on Aug 23, 2026

   

   nyecov

   on Aug 23, 2026

   Author

   More actions

   Tracing the build, the fix looks like a one-line change.

   .github/actions/setup-bun derives the toolchain version solely from package.json:

   V=$(node -p "require('./package.json').packageManager.split('@')[1]")
   url=https://github.com/oven-sh/bun/releases/download/bun-v${V}/bun-${OS}-x64-baseline.zip
   

   with bun-version-file: package.json for the non-baseline path. packages/opencode/script/build.ts then compiles via Bun.build({ compile: { target: "bun-windows-x64", ... } }), so the embedded runtime is whatever version of Bun runs the build.

   So bumping "packageManager": "bun@1.3.14" → "bun@1.4.0" should be sufficient to propagate the fix to every published target — no code change. bun-windows-x64.zip and bun-windows-x64-baseline.zip both exist on the bun-v1.4.0 release, so the baseline path resolves too. CONTRIBUTING already states "Requirements: Bun 1.3+", so 1.4.0 is within the supported range.

   Worth noting the beta and dev branches also still pin bun@1.3.14, so there's currently no channel where users can pick this up.
4. cwx07426 commented on Oct 10, 2026

   

   cwx07426

   on Oct 10, 2026

   More actions

   Additional reproduction: Yan Kernel (same embedded Bun 1.3.14, same crash)

   This is not specific to opencode — any product built on this kernel reproduces it. Confirmed on Yan Agent / Yan Kernel (Windows desktop), which ships the same opencode.exe runtime.

   Evidence from this machine:

   • Kernel binary: %APPDATA%\yan-agent\YanData\opencode-runtime\bin\all-file-tools-v1-344eedb423ef3c4d\opencode.exe, ProductVersion = 1.3.14 (embedded Bun 1.3.14).
   • Crash log (YanData\yan-core\events.jsonl):
     • 26 × panic(thread ...): Segmentation fault at address 0x3C
     • 31 × OpenCode exited during startup (3)
     • Crash report stack frames: npggNT64.des … USER32.dll … npggNT64.des — identical to Segfault at 0x3C — nProtect GameGuard (npggNT64.des) injection kills any Bun process on Windows 11 oven-sh/bun#34055.
   • Trigger: while nProtect GameGuard is running (local GameMon.des / GameMon64.des active). The kernel dies at startup, in bursts; recovers as soon as the game exits.

   Same root cause as this issue: embedded Bun 1.3.14 predates oven-sh/bun#35083 (first shipped in Bun 1.4.0). The fix path is the same — bump the pinned bun@1.3.14 to >=1.4.0 and rebuild the compiled binary. Any downstream consumer embedding this kernel is affected, so it would help to note that in the fix.

   Environment: Windows 11 26100, x64; kernel opencode 1.18.11 / Bun 1.3.14.
5. thdxr commented on Oct 11, 2026

   

   thdxr

   on Oct 11, 2026

   Member

   More actions

   Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.

   — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
6. thdxr

   closed this as not plannedon Oct 11, 2026