Codex app crashes unexpectedly while running.

Resolved 💬 2 comments Opened Jun 17, 2026 by yzhbradoodrrpurp Closed Jun 28, 2026

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

26.611.61753

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

Bug Description

Codex desktop app unexpectedly crashed while running. According to the macOS crash report, the crash happened in an internal git worker thread and appears to be caused by a Node/V8 out-of-memory abort.

The app terminated with SIGABRT after node::OOMErrorHandler was triggered.

Environment

  • Codex version: 26.611.61753 (4008)
  • Bundle ID: com.openai.codex
  • Platform: macOS
  • macOS version: 26.5.1 (25F80)
  • Device: MacBook Air M2 (Mac14,15)
  • Architecture: Apple Silicon ARM64
  • Process type: Native ARM64 (not translated through Rosetta)

Crash Summary

Process:             Codex
Path:                /Applications/Codex.app/Contents/MacOS/Codex
Identifier:          com.openai.codex
Version:             26.611.61753 (4008)

Exception Type:      EXC_CRASH (SIGABRT)
Termination Reason:  Namespace SIGNAL, Code 6, Abort trap: 6

Triggered by Thread: 51 git

Application Specific Information:
abort() called

Relevant Crashed Thread

Thread 51 Crashed:: git

0   libsystem_kernel.dylib
    __pthread_kill

1   libsystem_pthread.dylib
    pthread_kill

2   libsystem_c.dylib
    abort

3   Codex Framework
    node::OOMErrorHandler(char const*, v8::OOMDetails const&)

...

29  Codex Framework
    uv_run

30  Codex Framework
    node::SpinEventLoopInternal(node::Environment*)

31  Codex Framework
    node::worker::Worker::Run()

Observed Behavior

Codex immediately terminated after the internal Node/V8 runtime hit an OOM condition.

The crash appears related to background git processing:

  • crashed thread name: git
  • failure path: Node worker thread
  • abort source: node::OOMErrorHandler

Expected Behavior

Codex should handle large repositories, git operations, or memory pressure gracefully instead of terminating the entire application.

Possible expected behaviors:

  • stop/cancel the problematic git operation
  • show an error message
  • limit memory usage of the worker
  • recover the worker thread without crashing the UI

Additional Information

The app had been running for about 1.5 hours before crashing.

Launch Time:
2026-06-17 11:15:31

Crash Time:
2026-06-17 12:42:08

The crash happened on the following internal framework:

Codex Framework
Version: 149.0.7827.115

This seems like a memory leak or unbounded memory growth in the git worker / repository analysis process.

What steps can reproduce the bug?

I don't know.

What is the expected behavior?

Codex should handle large repositories, git operations, or memory pressure gracefully instead of terminating the entire application.

Additional information

Codex-2026-06-17-124221.txt

View original on GitHub ↗

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