Skip to content

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

Closed as not planned

Description

@stflj2022

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 (Missing sessions after update #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

Activity

  1. github-actions commented on Jul 27, 2026

    @github-actions
    Contributor

    This issue might be related to existing issues. Please check:

    If your crash is related to session history size or database growth, #38362 may be more directly relevant. If it reproduces on a fresh install with no prior data, it is likely a distinct issue.

  2. github-actions commented on Sep 27, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions