[macOS] Desktop app crashes with EXC_BAD_ACCESS in Codex Framework V8 path

Open 💬 1 comment Opened Jul 18, 2026 by dimasyankauskas

What version of the Codex App are you using?

26.715.31925 (build 5551)

What platform are you using?

macOS 26.5.2 on Apple Silicon (ARM64)

What issue are you seeing?

The Codex desktop app has crashed four times in the last two days, including after a long-running session.

macOS recorded EXC_BAD_ACCESS (SIGSEGV) with KERN_INVALID_ADDRESS. The crashing thread was the main browser/UI thread (CrBrowserMain). The visible stack frames were inside Codex Framework, including V8/JavaScript-runtime functions such as v8impl::Reference::InvokeFinalizerFromGC and v8::internal::ThreadIsolation::TryLookupJitPage.

This was a native segmentation fault, not an out-of-memory termination or a network error.

Steps to reproduce

I do not yet have a reliable minimal reproduction. The crashes occurred during normal desktop-app use, including after the app had remained open for several hours.

Expected behavior

The desktop app should remain stable during extended normal use.

Additional information

I have intentionally omitted the full crash report and all unique identifiers, local paths, workspace details, account information, and timestamps to avoid publishing personal data. I can provide a sanitized or full crash report privately if a maintainer requests it.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗