Repeated macOS Codex Desktop 26.609 crashes: CrBrowserMain EXC_BREAKPOINT, Renderer SIGABRT, stale app-server helpers
What version of the Codex App are you using (From “About Codex” dialog)?
Codex Desktop 26.609.30741Bundle version: 3808Bundled CLI: codex-cli 0.140.0-alpha.2Codex Framework / Chromium version in crash reports: 149.0.7827.54
What subscription do you have?
ChatGPT Pro
What platform is your computer?
macOS 26.5 beta on Apple Silicon MacBook Pro
What issue are you seeing?
Codex Desktop repeatedly crashes on macOS after recent 26.608 / 26.609 builds. This continued after reboot and has a consistent crash signature.
The main Codex process crashes with:
Exception: EXC_BREAKPOINT
Signal: SIGTRAP
Termination: SIGNAL 5 Trace/BPT trap: 5
Faulting thread: 0
Triggered thread name: CrBrowserMain
Queue: com.apple.main-thread
Around the same timestamp, the Codex Renderer crashes with:
Exception: EXC_CRASH
Signal: SIGABRT
Termination: SIGNAL 6 Abort trap: 6
Faulting thread: 0
This is not a single one-off crash. I found repeated crash reports on both 26.608 and 26.609:
2026-06-11 12:08:01 +0800 - Codex 26.608.12217 - EXC_BREAKPOINT / SIGTRAP
2026-06-11 13:17:58 +0800 - Codex 26.608.12217 - EXC_BREAKPOINT / SIGTRAP
2026-06-11 20:15:08 +0800 - Codex 26.608.12217 - EXC_BREAKPOINT / SIGTRAP
2026-06-11 23:26:01 +0800 - Codex 26.608.12217 - EXC_BREAKPOINT / SIGTRAP
2026-06-12 14:10:02 +0800 - Codex 26.609.30741 - EXC_BREAKPOINT / SIGTRAP
2026-06-12 16:29:09 +0800 - Codex 26.609.30741 - EXC_BREAKPOINT / SIGTRAP
2026-06-12 19:11:43 +0800 - Codex 26.609.30741 - EXC_BREAKPOINT / SIGTRAP
2026-06-12 20:15:46 +0800 - Codex 26.609.30741 - EXC_BREAKPOINT / SIGTRAP
2026-06-12 20:42:50 +0800 - Codex 26.609.30741 - EXC_BREAKPOINT / SIGTRAP
2026-06-12 20:53:37 +0800 - Codex 26.609.30741 - EXC_BREAKPOINT / SIGTRAP
2026-06-12 21:30:05 +0800 - Codex 26.609.30741 - EXC_BREAKPOINT / SIGTRAP
Latest main crash report: Codex-2026-06-12-213009.ips
Top triggered frames include:
rust_png$cxxbridge1$194$Reader$has_trns_chunk
node::inspector::NodeInspectorClient::startRepeatingTimer(...)
temporal_rs_PlainDateTime_second
cppgc::internal::EnsureGCInfoIndexTrait::EnsureGCInfoIndex(...)
v8::Integer::New(...)
v8::internal::ThreadIsolation::LookupJitPageLocked(...)
Latest renderer crash report: Codex (Renderer)-2026-06-12-213006.ips
Renderer top frames:
__pthread_kill
pthread_kill
abort
abort_report_np
main
What steps can reproduce the bug?
I do not yet have a minimal deterministic repro, but the crashes happened while using Codex Desktop with:
- Multiple Codex threads/projects active.
- Browser / Computer Use / Simulator-related tools available or recently used.
- iOS Simulators and xcodebuildmcp helpers active in the background.
- Codex Desktop running after the 26.608 / 26.609 updates.
The issue continued after reboot.
What is the expected behavior?
Codex Desktop should not crash the whole app when Browser / Renderer / helper tooling is active. If memory pressure or stale helpers are present, Codex should fail gracefully, clean up helper processes, or warn the user rather than leaving orphaned app-server trees and repeated crash reports.
Additional information
Additional diagnostics:
- OpenAI status page showed services operational during investigation.
- The app signature appears valid and notarized:
spctl --assess --verbose=4 /Applications/Codex.app
# /Applications/Codex.app: accepted
# source=Notarized Developer ID
codesign --verify --deep --strict --verbose=2 /Applications/Codex.app
# valid on disk / satisfies Designated Requirement
- Memory pressure was present during the crash window:
- Swap observed around 5.2 GB before cleanup.
- Physical memory was near full usage.
- Two iOS Simulators were booted and multiple Simulator / xcodebuildmcp / Computer Use helpers were active.
- After a crash/restart, I found a stale orphaned Codex app-server:
PID 838
PPID 1
/Applications/Codex.app/Contents/Resources/codex app-server --analytics-default-enabled
- That orphaned app-server had many long-lived helper children, including node_repl, xcodebuildmcp, SkyComputerUseClient, local dev servers, and stdio app-server children.
- Cleaning the orphaned app-server tree and shutting down booted Simulators reduced swap from about 5.2 GB to about 2.4 GB.
- However, the repeated CrBrowserMain / EXC_BREAKPOINT signature suggests this is not only a one-off local overload.
Related issues:
- #27349 - Codex Desktop crashes when Browser opens in one thread while other non-Browser threads are active
- #27599 - Codex Desktop repeatedly crashes with EXC_BREAKPOINT/SIGTRAP and VM fault symptoms
- #26869 - Codex Desktop app-server leaks child processes and writes excessive logs after crash/restart
- #27848 - Codex Desktop 26.609.30741 fully saturates CPU/RAM after Jun 11 update
I can provide the full .ips crash reports if needed. I am not attaching them publicly yet because they may contain local paths, timestamps, process command lines, and local username.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗