anomalyco / anomalyco/opencode

V8 OOM Crash on Linux - Renderer Process Exits with Code 4

Open
#39,055 1 comment 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Jul 27, 2026.

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

Description

Description

Summary

OpenCode Desktop consistently crashes approximately 30-35 seconds after launch
on Debian Linux. The renderer process exits with code 4 due to V8 Zone memory
exhaustion, despite system having ample available RAM (9GB free of 14GB
total).

Environment

  • OpenCode Version: 1.18.6
  • Electron Version: 42.3.3
  • Operating System: Debian GNU/Linux 13 (trixie)
  • Architecture: x86_64
  • Installation Method: AppImage (opencode-desktop-linux-x86_64.AppImage)
  • CPU: AMD Ryzen 7 4800U with Radeon Graphics

Steps to Reproduce

  1. Launch OpenCode Desktop via AppImage:
    ./opencode-desktop-linux-x86_64.AppImage
    
  2. Wait approximately 30-35 seconds
  3. Application window opens but crashes shortly after

Actual Behavior

The renderer process crashes with the following errors in logs:

[ERROR:third_party/blink/renderer/bindings/core/v8/v8_initializer.cc:948] V8
process OOM (Zone).
[ERROR:mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:748] Message
4 rejected by interface blink.mojom.WidgetHost
(window) app render process gone {
url: 'oc://renderer/index.html',
details: { reason: 'crashed', exitCode: 4 }
}

Expected Behavior

Application should run normally without crashing.

Workarounds Attempted (None Successful)

  • --disable-gpu flag
  • --disable-dev-shm-usage flag
  • --no-sandbox flag
  • --js-flags="--max-old-space-size=4096" flag
  • Clearing application cache and user data

System Status

$ free -h
内存: 14Gi 5.0Gi 5.2Gi 300Mi 5.7Gi
9Gi

Additional Context

  • FUSE is installed and working
  • All required libraries are present
  • Only the renderer process crashes; main process continues running
  • Multiple crash dumps accumulate in
    ~/.config/ai.opencode.desktop/Crashpad/pending/
  • Note: There is a separate AMD Ryzen issue (#39064) for SIGILL crashes - this
    is a different V8 OOM issue
Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

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.