Bug: Bun JIT crash (Segmentation fault) caused by enterprise security DLL injection

[neostfox]

Description

When running opencode.exe in corporate environments with strict Enterprise Security software (e.g., QiAnXin / LHShield), the injected --use-system-ca flag causes the underlying Bun JIT engine to crash with a Segmentation fault due to DLL injection conflicts.
Crash Log:

Windows v.win11_zn
CPU: sse42 avx avx2
Args: "C:\Users\11829515\scoop\apps\opencode\current\opencode.exe" "--user-agent=opencode/1.2.11" "--use-system-ca" "--" "-v"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) fetch(2) jsc standalone_executable
Builtins: "bun:ffi" "bun:main" "bun:sqlite" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:console" "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:stream" "node:stream/promises" "node:string_decoder" "node:timers" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "undici" "node:v8" "node:http2" "node:diagnostics_channel" "node:dgram"
Elapsed: 703ms | User: 1500ms | Sys: 546ms
RSS: 0.54GB | Peak: 0.54GB | Commit: 0.87GB | Faults: 197347 | Machine: 34.06GB

panic(main thread): Segmentation fault at address 0x20F166520B8
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.10/ea26b1d6c7EugogCCYKERNEL32.DLLilzFCcLHShield64.dll0uknCCcLHShield64.dllw5whCCcLHShield64.dll6hoOCcLHShield64.dllmhjTCcLHShield64.dllwgVCcLHShield64.dlls45tCCcLHShield64.dllizxfCcLHShield64.dll66mfCcLHShield64.dlloyyyB++ptxBi9ntxB4li1iB6pupiB__6471wCA2+gBwrw0sW
...

Plugins

N/A

OpenCode version

1.2.11

Root Cause:

Enterprise DLP/Security software forcibly injects its monitoring DLL (LHShield64.dll) into the process when network API hooks are triggered (due to the system CA flag). This corrupts Bun's memory space.

Steps to reproduce

Run the CLI in a Windows environment restricted by LHShield Enterprise Security.

opencode.exe -v

Screenshot and/or share link

Operating System

Windows 11 22H2

Terminal

pwsh

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• OpenCode version is left as _No response_ — please fill in the version (e.g. from opencode --version)
• Steps to reproduce is left as _No response_ — please describe what you were doing when the crash occurred (e.g. starting opencode, running a specific command, etc.)
• Operating System is left as _No response_ — the crash log mentions Windows 11, please confirm and fill in this field

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

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

• Windows segfault: Bun 1.3.9 crash during active multi-tool session (no graceful shutdown) #14204: Windows segfault with Bun 1.3.9 crash during an active opencode session on Windows 11 x64 — very similar crash signature and environment

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thanks for updating the issue! It now includes all the required information — a clear description, crash log, steps to reproduce, version, OS, and a screenshot. The needs:compliance label has been removed.