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

Open
#34,084 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
macos
Domain
desktop, operating-systems

Research direction

No source file, test, or reliable reproduction entry point is identified. Start with the sanitized crash report and the Codex Framework/V8 stack frames described in the issue; a useful fix would require a reproducible EXC_BAD_ACCESS failure and verification that extended macOS use is stable.

Written by the indexing model from the issue text.

Description

app bug
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.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.