Electrobun BrowserWindow and GPUWindow crash on Windows 11 (GPU process exit_code=143)

[devallibus]

Summary

Both Electrobun BrowserWindow (CEF) and GPUWindow (WGPU) paths crash immediately on Windows 11 when launched from the electrobun-counter example. No window is ever rendered. The CEF GPU subprocess exits with code 143, taking down the app.

Environment

• OS: Windows 11 Pro 10.0.26200 (x86_64)
• Electrobun: 1.15.1
• Bun: 1.3.8
• GPUs: NVIDIA GeForce RTX 5070 (driver 32.0.15.9186), AMD Radeon Graphics (driver 32.0.11024.2)

Reproduction

cd examples/electrobun-counter
bun install
bun run dev:electrobun:hybrid   # BrowserWindow path
# OR
bun run dev:electrobun:gpu      # GPUWindow path

BrowserWindow (CEF) error

[CEF] Created job object for process tracking
[CEF] Using path: C:\Users\...\dev\CEF
DevTools listening on ws://127.0.0.1:9222/devtools/browser/...
[ERROR:content\browser\gpu\gpu_process_host.cc:996] GPU process exited unexpectedly: exit_code=143
[ERROR:content\browser\network_service_instance_impl.cc:610] Network service crashed or was terminated
Child process exited with code: 143

The CEF process starts, DevTools port opens, but the GPU subprocess crashes before any window is rendered.

GPUWindow (WGPU) error

WGPU latest already cached for win-x64
Copied WGPU library to bundle: ...\webgpu_dawn.dll
Copied d3dcompiler_47.dll to bundle: ...
[LAUNCHER] Loading app code from flat files
Child process exited with code: 143

The webgpu_dawn.dll and d3dcompiler_47.dll are copied, the launcher loads gpu.ts, but the bun child process dies silently with code 143.

Notes

• Vite dev server starts fine and serves the page at localhost:1420
• WASM build completes successfully
• All webtau adapter unit tests pass (64 tests via mocks)
• The electrobun.exe binary (v1.15.1) is present and runs, but no window appears
• This machine has dual GPUs (integrated AMD + discrete NVIDIA RTX 5070) — the GPU process crash may be related to GPU selection or driver compatibility
• Electrobun's README claims Windows 11+ as "Official" platform support

Likely upstream

This is almost certainly an Electrobun issue, not a gametau issue. The crash happens in CEF's GPU process host (gpu_process_host.cc:996) before any gametau/webtau code runs. Consider filing upstream at https://github.com/nicholasgasior/nicholasgasior/issues if reproducible on other Windows machines.

Impact on v0.7.0

The Electrobun adapter code, WASM builds, and Rust compilation are all verified and correct. Only the actual Electrobun runtime on Windows is affected. macOS/Linux testing is tracked in #173.