[macOS] Codex app 26.831.21537 crashes with EXC_BREAKPOINT/SIGTRAP on Chrome_IOThread

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

26.831.21537 (build 7579), from the macOS crash report

What subscription do you have?

prolite (reported account plan type)

What platform is your computer?

macOS 26.6.2 (25G83); Apple M4 Pro; Mac16,7; 24 GB RAM; ARM64 native. uname -mprs: Darwin 25.6.0 arm64 arm

What issue are you seeing?

The desktop app crashed on September 2, 2026, approximately 6 minutes 2 seconds after launch. The macOS report identifies the process as ChatGPT at /Applications/ChatGPT.app/Contents/MacOS/ChatGPT, with bundle identifier com.openai.codex.

Observed crash details

• Crash time: 2026-09-02 13:13:44.7740 -0400 (EDT).
• Launch time: 2026-09-02 13:07:42.7782 -0400.
• Process role in report: Background.
• Faulting thread: 20 Chrome_IOThread.
• Exception: EXC_BREAKPOINT (SIGTRAP).
• Exception codes: 0x0000000000000001, 0x000000011d8a0c60.
• Termination: Namespace SIGNAL, Code 5, Trace/BPT trap: 5.
• System Integrity Protection: enabled.
• Codex Framework: 152.0.7977.64 (build 7977.64).
• Framework binary UUID: 4c4c4420-5555-3144-a191-1e4ed438dd5e.
• Top frame image offset: 145591392 bytes into Codex Framework, for symbolication.

Thread 20 Crashed:: Chrome_IOThread
0   Codex Framework               	       0x11d8a0c60 node::inspector::protocol::BinaryValue::asBinary(node::inspector::protocol::Binary*) const + 17627884
1   Codex Framework               	       0x11d8a0c78 node::inspector::protocol::BinaryValue::asBinary(node::inspector::protocol::Binary*) const + 17627908
2   Codex Framework               	       0x11d8a0c94 node::inspector::protocol::BinaryValue::asBinary(node::inspector::protocol::Binary*) const + 17627936
3   Codex Framework               	       0x11d8a3e54 node::inspector::protocol::BinaryValue::asBinary(node::inspector::protocol::Binary*) const + 17640672
4   Codex Framework               	       0x11d8a1158 node::inspector::protocol::BinaryValue::asBinary(node::inspector::protocol::Binary*) const + 17629156
5   Codex Framework               	       0x114ddf294 cxxbridge1$string$ptr + 24148
6   Codex Framework               	       0x114dddfb4 cxxbridge1$string$ptr + 19316
7   Codex Framework               	       0x1168b22e8 v8::CpuProfileNode::GetDeoptInfos() const + 380896
8   Codex Framework               	       0x114de5ecc cxxbridge1$slice$new + 15892
9   Codex Framework               	       0x1164ec668 v8::Object::SetAccessorProperty(v8::Local<v8::Name>, v8::Local<v8::Function>, v8::Local<v8::Function>, v8::PropertyAttribute) + 23336
10  Codex Framework               	       0x115449260 v8::StackTrace::CurrentScriptData(v8::Isolate*, std::__Cr::span<v8::StackTrace::ScriptData, 18446744073709551615ul>) + 181984
11  Codex Framework               	       0x11570611c rust_png$cxxbridge1$197$Reader$interlaced + 280140
12  Codex Framework               	       0x115704374 rust_png$cxxbridge1$197$Reader$interlaced + 272548
13  Codex Framework               	       0x115af4cb8 v8::Value::Int32Value(v8::Local<v8::Context>) const + 141136
14  Codex Framework               	       0x116c4a268 v8::Isolate::Initialize(v8::Isolate*, v8::Isolate::CreateParams const&) + 184040
15  Codex Framework               	       0x116c49b58 v8::Isolate::Initialize(v8::Isolate*, v8::Isolate::CreateParams const&) + 182232
16  Codex Framework               	       0x1186d01b4 v8impl::Reference::InvokeFinalizerFromGC() + 34084
17  Codex Framework               	       0x116e09400 v8::Object::GetCreationContext(v8::Isolate*) + 16808
18  Codex Framework               	       0x116492ab0 v8::internal::ThreadIsolation::LookupJitPageLocked(unsigned long, unsigned long) + 40320
19  libsystem_pthread.dylib       	       0x1883f7c58 _pthread_start + 136
20  libsystem_pthread.dylib       	       0x1883f2c1c thread_start + 8

The exception and stack identify the failure location; the root cause is not established from this report alone. The exported symbol labels and large offsets should not be treated as a confirmed source-level diagnosis.

What steps can reproduce the bug?

A reliable minimal reproduction is not known yet. The supplied crash report documents this sequence:

1. The app launched at 13:07:42 EDT on September 2, 2026.
2. Approximately 6 minutes 2 seconds later, its main process terminated with the signature above.
3. macOS generated the attached crash report.

The action immediately before the crash and the recurrence frequency have not yet been provided. One occurrence is documented here; this does not establish that the crash happened only once. No specific prompt, workspace operation, model, or feature has been identified as the trigger.

What is the expected behavior?

The desktop app should remain running. A background operation failing should be handled without terminating the entire app.

Additional information

Possibly related: #27599, including its later reports of Chrome_IOThread / EXC_BREAKPOINT crashes. This report adds app build 26.831.21537 (7579) / framework 152.0.7977.64 on macOS 26.6.2. I have not established that it shares the original issue's generated-output or Git-worker trigger.

Please symbolicate the faulting frame for this exact framework build and investigate the underlying fatal path. If this is the same issue, please link or consolidate this report with #27599.

A redacted copy of the supplied macOS crash report is attached. It preserves stack frames, binary UUIDs, versions, and timestamps. Device/vendor identifiers, crash-reporter identifiers, incident/boot/sleep identifiers, local user ID, log-writing signature, and OS experiment metadata were removed. No conversation history or workspace contents are included.

codex-macos-crash-2026-09-02-redacted.txt

Start with the attached redacted crash report and the faulting frame in Codex Framework build 152.0.7977.64, using its UUID and offset for symbolication. Compare the Chrome_IOThread/EXC_BREAKPOINT details with issue #27599, then establish a reproducible trigger or root cause. Done means the crash is explained and fixed, or this report is linked or consolidated if it is the same issue.