Codex Desktop 26.623.61825 crashes with EXC_BREAKPOINT/SIGTRAP in CrBrowserMain on macOS 27.0

Open 💬 2 comments Opened Jun 29, 2026 by huangdijia

What version of the Codex App are you using (From “About Codex” dialog)?

Codex Desktop 26.623.61825 build 4548

Codex Framework / Chromium in crash report: 149.0.7827.197

What subscription do you have?

Unknown / not relevant to local crash report.

What platform is your computer?

  • macOS 27.0 (26A5368g)
  • Apple Silicon / ARM64
  • Hardware Model: Mac16,10
  • Memory: 24 GB
  • Displays: two external 4K Dell displays attached

What issue are you seeing?

Codex Desktop quit unexpectedly while running in the background after about 24 minutes of uptime.

Crash summary from the macOS report:

Process:             Codex
Path:                /Applications/Codex.app/Contents/MacOS/Codex
Identifier:          com.openai.codex
Version:             26.623.61825 (4548)
Code Type:           ARM-64 (Native)
Role:                Background
Date/Time:           2026-06-29 18:11:16.7011 +0800
Launch Time:         2026-06-29 17:47:43.6797 +0800
OS Version:          macOS 27.0 (26A5368g)
Triggered by Thread: 0 CrBrowserMain, Dispatch Queue: com.apple.main-thread
Exception Type:      EXC_BREAKPOINT (SIGTRAP)
Exception Codes:     0x0000000000000001, 0x000000011f259e3c
Termination Reason:  Namespace SIGNAL, Code 5, Trace/BPT trap: 5
Incident Identifier: 72CD149B-2A22-469A-9686-B992905104FD

Top of the crashing thread:

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0   Codex Framework  0x11f259e3c ares_llist_replace_destructor + 2259972
1   Codex Framework  0x11ce4b490 v8::ToExternalPointerTag(unsigned short) + 468
2   Codex Framework  0x11ce4b41c v8::ToExternalPointerTag(unsigned short) + 352
3   Codex Framework  0x11b60b3c0 v8::internal::ThreadIsolation::UnregisterWasmAllocation(unsigned long, unsigned long) + 273416
4   Codex Framework  0x119f4472c v8::internal::compiler::CompilationDependencies::DependOnArraySpeciesProtector() + 106396
5   Codex Framework  0x118d611c0 v8::CodeEvent::GetScriptColumn() + 76288
6   Codex Framework  0x118d60f6c v8::CodeEvent::GetScriptColumn() + 75692
7   Codex Framework  0x120cda328 uv_os_getpid + 3868
8   Codex Framework  0x1193bafa0 v8::Promise::Resolver::Reject(v8::Local<v8::Context>, v8::Local<v8::Value>) + 174572
9   Codex Framework  0x118b3b954 cxxbridge1$string$drop + 61384
10  Codex Framework  0x118b3b438 cxxbridge1$string$drop + 60076
11  Codex Framework  0x1184efda0 v8::internal::ThreadIsolation::TryLookupJitPageLocked(unsigned long, unsigned long) + 83136
12  Codex Framework  0x119bc3dc8 rust_png$cxxbridge1$194$Reader$get_iccp_chunk + 129812
13  Codex Framework  0x119bc3604 rust_png$cxxbridge1$194$Reader$get_iccp_chunk + 127824
14  Codex Framework  0x119bc3490 rust_png$cxxbridge1$194$Reader$get_iccp_chunk + 127452

Later frames include V8/Node and Rust image/temporal symbols, then ChromeMain and main.

A few native modules were loaded in the process:

better_sqlite3.node
sparkle.node
sky.node
browser-use-peer-authorization.node
devicecheck.node

System log entries immediately before the crash do not show a clear Codex fatal/assert message. The only notable nearby errors were CoreSpotlight/Biome donation errors around 18:11:12, about four seconds before the crash:

2026-06-29 18:11:12.116 Codex[...] [com.apple.corespotlight:index]
Failed to request donation Error Domain=CSIndexErrorDomain Code=-1000 "Failed to request donation"

I am not sure this CoreSpotlight error is causal; it is included only because it is the only nearby system log error before the crash.

What steps can reproduce the bug?

I do not yet have a deterministic minimal reproduction.

Observed sequence:

  1. Launch Codex Desktop 26.623.61825 on macOS 27.0 (26A5368g).
  2. Use Codex normally.
  3. Leave the app running in the background.
  4. After about 24 minutes, Codex unexpectedly quits.
  5. macOS records EXC_BREAKPOINT / SIGTRAP on Thread 0 CrBrowserMain.

What is the expected behavior?

Codex Desktop should keep running. If a Chromium/V8/Node/native-module operation fails, it should fail gracefully without terminating the main app process.

Additional information

This looks related to the recent family of Codex Desktop macOS crashes with EXC_BREAKPOINT / SIGTRAP on CrBrowserMain, but this report is for a newer app build and newer macOS build:

  • #30531 reports crashes on 26.623.61825, but without crash details.
  • #30005 reports CrBrowserMain startup crashes on 26.616.81150.
  • #27880 reports repeated CrBrowserMain / EXC_BREAKPOINT crashes on 26.608 / 26.609.
  • #28274 and #26863 also include similar macOS CrBrowserMain crash signatures.

I am not attaching the full raw crash report publicly because it contains machine identifiers and local runtime details, but I can provide a redacted .ips excerpt if helpful.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗