Codex App repeatedly crashes in git worker with node::OOMErrorHandler on macOS

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

26.602.40724 (3593)

What subscription do you have?

Unknown / not included in the crash report. I can provide this privately if needed.

What platform is your computer?

Darwin 25.5.0 arm64 arm
macOS 26.5 (25F71)

What issue are you seeing?

The Codex Desktop app repeatedly exits/crashes on macOS. The crash reports consistently point to a git worker thread aborting from Node/V8 OOM handling.

High-signal crash details, with personal paths redacted:

Process:             Codex
Identifier:          com.openai.codex
Version:             26.602.40724 (3593)
Code Type:           ARM-64 (Native)
OS Version:          macOS 26.5 (25F71)
Exception Type:      EXC_CRASH (SIGABRT)
Termination Reason:  Namespace SIGNAL, Code 6, Abort trap: 6
Triggered by Thread: 51 git
Thread 51 Crashed::  git
node::OOMErrorHandler(char const*, v8::OOMDetails const&)

One recent crash report was dated 2026-06-07 21:24 +0800. Earlier reports showed the same signature.

What steps can reproduce the bug?

I do not yet have a minimal reproduction, but the crashes happen while using Codex Desktop in local workspaces under ~/Documents/Codex/....

Local context that may be relevant:

1. Earlier, git rev-parse --show-toplevel from a Codex workspace resolved to ~, so Codex may have treated the whole home directory as the repository root.
2. The home-level ~/.git repository is very large: approximately 18G, with about 34953 loose objects reported by git --git-dir=~/.git count-objects -vH.
3. I added smaller git boundaries with git init under ~/Documents/Codex and the current workspace, so new workspaces should no longer climb to ~ as the git root.
4. A recent crash report still shows the same Thread 51 git + node::OOMErrorHandler signature. I am not yet certain whether that was after a full app restart with the new boundaries active.

What is the expected behavior?

Codex Desktop should not hard-crash when its git worker encounters a very large repository, a large number of loose objects, or an overly broad parent git root. If git scanning exceeds memory/time limits, the app should fail gracefully, limit the scan scope, or surface a recoverable error.

Additional information

I searched public issues and found related Codex Desktop crash / git sync reports, but did not find an exact duplicate for this signature: Thread 51 git + node::OOMErrorHandler. I am not attaching full crash logs publicly because they may contain private local paths or session details. I can provide redacted crash reports or logs if maintainers need them.