anomalyco / anomalyco/opencode

[Bug]: Windows app fails to launch — GPU & Renderer process crash with exitCode -2147483645 on AMD Radeon graphics

Open
#48,747 4 comments 1 reaction 1 assignee View on GitHub

@Hona is already working on this.

Since Sep 13, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

After installing OpenCode Desktop on Windows, the app fails to open or opens to a crashed blank screen with an
option to export logs. The GPU process crashes repeatedly in the background, which subsequently crashes the window
renderer process with exit code -2147483645 (0x80000003 / STATUS_BREAKPOINT).

### Environment & System Info
- **App Version**: 1.18.30 (packaged)
- **OS**: Windows 10/11 (win32 x64)
- **Electron**: 42.3.3
- **Chromium**: 148.0.7778.218
- **Node**: 24.15.0
- **GPU**: AMD Radeon(TM) 820M Graphics
- **Driver Version**: 32.0.22032.3003

---

### Relevant Log Snippets

From **`utility.log`**:
```json
[error] (utility) child process gone {
  details: {
    type: 'GPU',
    reason: 'crashed',
    exitCode: -2147483645,
    serviceName: 'GPU'
  }
}

(Crashes 4–5 times in rapid succession on startup)

From window.log:

[error] (window) app render process gone { url: '', details: { reason: 'crashed', exitCode: -2147483645 } }
[error] (window) renderer process gone {
  window: '03493032-104f-4f96-992f-6b5dfe41af4f',
  currentURL: '',
  details: { reason: 'crashed', exitCode: -2147483645 }
}

──────

Root Cause Analysis

In Electron 42 / Chromium 148, the experimental Skia Graphite / Vulkan / Dawn backend appears to hit a fatal
breakpoint assertion (STATUS_BREAKPOINT / 0x80000003) during GPU initialization on Windows AMD Radeon drivers. When
the GPU process crashes multiple times, the renderer process fails and the window dies.
──────

Tested Workarounds
  1. --disable-gpu:
    The app opens and runs, but UI interactions, syntax highlighting, and scrolling suffer from heavy lag due to CPU
    software rasterization.
  2. --use-angle=d3d11 --disable-features=Vulkan,SkiaGraphite (Optimal Workaround):
    Forcing the ANGLE Direct3D 11 backend completely resolves the crash while maintaining smooth 60fps hardware GPU
    acceleration.
Suggested Fix

Consider configuring the Windows Chromium flags in Electron to default to the stable D3D11 ANGLE backend (--use-
angle=d3d11) or disable the experimental Vulkan/Graphite pipeline on Windows if compatible hardware drivers are not
detected.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.