[macOS][26.908.40834] ChatGPT/Codex crashes with EXC_BAD_ACCESS in v8::Object::GetCreationContextChecked

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

ChatGPT desktop app 26.908.40834 (build 8881), shown as Powered by Codex & OWL and released Sep 11, 2026.

What subscription do you have?

ChatGPT Pro.

What platform is your computer?

• macOS 26.6.2 (25G83)
• MacBook Pro 16-inch (Mac17,6)
• Apple M5 Max
• ARM64 native
• 128 GB RAM
• System Integrity Protection enabled

What issue are you seeing?

While I was actively using Codex normally in the macOS desktop app, the entire application suddenly terminated. macOS displayed the system crash dialog: “ChatGPT quit unexpectedly.”

This was not an ordinary model, task, or session error inside the UI. The desktop process itself exited, interrupting the active workflow and requiring the application to be reopened.

Sanitized crash metadata:

Process:             ChatGPT
Identifier:          com.openai.codex
Version:             26.908.40834 (8881)
Code Type:           ARM-64 (Native)
Role:                Foreground

Triggered by Thread: 0  CrBrowserMain, Dispatch Queue: com.apple.main-thread
Exception Type:      EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype:   KERN_INVALID_ADDRESS
Termination Reason:  Namespace SIGNAL, Code 11, Segmentation fault: 11

Top of the crashed stack:

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0   Codex Framework  v8::Object::GetCreationContextChecked(v8::Isolate*) + 12
1   Codex Framework  node::PrincipalRealm::primordials() const + 522656
2   Codex Framework  node::PrincipalRealm::primordials() const + 607304
3   Codex Framework  ares_llist_replace_destructor + 460640
4   Codex Framework  v8::External::New(v8::Isolate*, void*, unsigned short) + 94308
5   Codex Framework  v8::Isolate::GetDataFromSnapshotOnce(unsigned long) + 18260
6   Codex Framework  cppgc::internal::CrossThreadPersistentRegion::~CrossThreadPersistentRegion() + 131436
7   Codex Framework  v8::ValueDeserializer::ReadValue(v8::Local<v8::Context>) + 729320

The stack shows that the crash occurred in a Codex Framework/V8 path. This is an observation from the Apple crash report, not a definitive root-cause claim.

What steps can reproduce the bug?

I do not yet have a deterministic minimal reproduction.

1. Launch the current macOS ChatGPT/Codex desktop app.
2. Open and use a Codex session normally.
3. During use, the application may suddenly terminate without an in-app warning.
4. macOS displays the “ChatGPT quit unexpectedly” crash reporter.

The app had remained running for an extended period before this occurrence. I have observed this exact crash at least once; the exception and stack signature above may be the most useful reproduction clues.

What is the expected behavior?

The desktop app should remain stable during normal and extended Codex use. If an internal browser, V8, or native-framework operation fails, the failure should be contained rather than terminating the entire application and interrupting the active workflow. The active task should also remain recoverable after reopening the app.

Additional information

• Codex Framework version in the report: 152.0.7977.83.
• The full Apple crash report contains the complete thread list, ARM thread state, binary images, and system configuration. I retained it and can provide a sanitized or full copy privately if requested.
• Screenshots were captured of the macOS crash dialog, the app About dialog, and the Mac hardware/OS information. They are not attached publicly because they contain unique device and crash identifiers.
• Related: #34084 reports an EXC_BAD_ACCESS crash in CrBrowserMain through a Codex Framework/V8 path, but on the older app version 26.715.31925 and with a different visible top-of-stack signature. This report adds the current 26.908.40834 build and the exact v8::Object::GetCreationContextChecked crash frame.
• Also distinct from #41618, which involved the older app version 26.825.41651 and EXC_BREAKPOINT (SIGTRAP) rather than this EXC_BAD_ACCESS (SIGSEGV) signature.

Privacy-sensitive values such as the Mac serial number, Crash Reporter Key, Incident Identifier, device identifiers, and exact memory addresses have intentionally been omitted from this public report.

Start with the retained Apple crash report and the CrBrowserMain stack, especially v8::Object::GetCreationContextChecked and the Codex Framework/V8 frames. Compare this signature with related issues #34084 and #41618, noting their different versions and exception types. Done means the crash cause is identified and normal or extended use no longer terminates the desktop app or loses the active task.