Summary
On some occasions during normal coding use, the Electron renderer suddenly exits with SIGTRAP (signal 5). There is no consistent trigger or obvious pattern so far.
This has occurred under both X11 and native Wayland. It also happens with GPU compositing disabled and enabled, so it does not appear to be exclusively a Wayland or GPU-compositing issue.
Observed behavior
There have been seven relevant SIGTRAP occurrences for /opt/codex-desktop/electron.
X11 occurrence
Process type: renderer
Signal: 5 (TRAP)
Relevant flags:
--ozone-platform=x11
--disable-gpu-compositing
Wayland occurrence
Process type: renderer
Signal: 5 (TRAP)
Relevant flags:
--ozone-platform=wayland
GPU compositing was enabled during the Wayland occurrence.
Around the latest occurrence, I found no OOM event, NVIDIA Xid, kernel GPU reset, or KWin crash in the system journal.
Reproduction
There is not yet a deterministic action sequence:
- Start the packaged Codex desktop app.
- Use it normally for coding and conversations.
- On some occasions, without a consistent trigger, the app suddenly becomes unresponsive or crashes.
- An Electron renderer process exits with
SIGTRAP (signal 5).
Environment
codex-desktop package: 2026.07.15.214550
Current installed port build commit: 4f0470de99f842b44fb848a169a191352e907cd1
Port version: 0.10.1
Upstream app: 26.707.72221
Electron: 42.1.0
OS: Ubuntu 26.04 LTS x86_64
Kernel: 7.0.0-27-generic
Desktop: KDE Plasma 6.6.5
GPU: NVIDIA GeForce RTX 3090
NVIDIA driver: 595.71.05
Currently enabled optional features:
- pet-overlay
- open-target-discovery
The occurrences may span multiple local rebuilds, but both the X11 and Wayland cases came from /opt/codex-desktop/electron and identified the exiting process as the renderer.
Expected behavior
The renderer should remain stable during normal use, or recover cleanly if a renderer process exits.
Related issues
This appears different from #1008. That report describes a KDE Wayland/NVIDIA compositor or whole-desktop freeze. This issue is a renderer SIGTRAP and also occurs under X11.
Issue #892 may be adjacent because it contains WebContents/lifecycle errors, but it does not report a renderer SIGTRAP.
Question
Would testing with a newer Electron 42.x release be useful, or is there a recommended way to enable additional renderer crash diagnostics?
Summary
On some occasions during normal coding use, the Electron renderer suddenly exits with
SIGTRAP (signal 5). There is no consistent trigger or obvious pattern so far.This has occurred under both X11 and native Wayland. It also happens with GPU compositing disabled and enabled, so it does not appear to be exclusively a Wayland or GPU-compositing issue.
Observed behavior
There have been seven relevant SIGTRAP occurrences for
/opt/codex-desktop/electron.X11 occurrence
Wayland occurrence
GPU compositing was enabled during the Wayland occurrence.
Around the latest occurrence, I found no OOM event, NVIDIA Xid, kernel GPU reset, or KWin crash in the system journal.
Reproduction
There is not yet a deterministic action sequence:
SIGTRAP (signal 5).Environment
The occurrences may span multiple local rebuilds, but both the X11 and Wayland cases came from
/opt/codex-desktop/electronand identified the exiting process as the renderer.Expected behavior
The renderer should remain stable during normal use, or recover cleanly if a renderer process exits.
Related issues
This appears different from #1008. That report describes a KDE Wayland/NVIDIA compositor or whole-desktop freeze. This issue is a renderer SIGTRAP and also occurs under X11.
Issue #892 may be adjacent because it contains WebContents/lifecycle errors, but it does not report a renderer SIGTRAP.
Question
Would testing with a newer Electron 42.x release be useful, or is there a recommended way to enable additional renderer crash diagnostics?