Codex desktop repeatedly aborts with V8 out-of-memory in internal git worker #30376

Summary

Codex Desktop crashes repeatedly during longer local sessions. macOS crash reports show an intentional SIGABRT from Node/V8's out-of-memory handler rather than an MCP server or child-process crash.

Environment

• Codex: 26.623.42026 (build 4514)
• macOS: 26.5.1 (25F80)
• Hardware: Mac14,12, Apple Silicon (ARM64)

Frequency

Six Codex crash reports were generated on June 27, 2026: 07:36:19, 07:51:16, 09:05:42, 09:09:15, 12:49:47, and 13:23:43.

All six reports contain node::OOMErrorHandler and terminate with EXC_CRASH / SIGABRT / Abort trap: 6.

Latest crash evidence

The latest report is Codex-2026-06-27-132343.ips. Its faulting thread is named git and the crashing frames begin:

__pthread_kill -> pthread_kill -> abort -> node::OOMErrorHandler

No Git command was requested or run in the conversation; the git name appears to identify an internal Codex worker.

Reproduction context

1. Work in a long-running local Codex thread with many completed turns.
2. Perform ordinary source inspection and MCP/tool calls with bounded outputs.
3. Continue the thread for an extended period.
4. Codex abruptly exits without an in-app error, then macOS writes an .ips crash report.

The latest crash occurred while Codex was reading its official troubleshooting manual and inspecting local Codex log filenames. The same signature occurred five times earlier that day across other activity.

Expected behavior

Long threads and internal Git/status processing should remain bounded in memory, or the app should recover from worker memory exhaustion without terminating the entire desktop process.

Actual behavior

A worker reaches the V8 heap limit and calls abort(), terminating Codex. There is no visible recovery prompt or useful in-app crash message.

Logs

App logs exist under ~/Library/Logs/com.openai.codex/2026/06/27 and macOS crash reports under ~/Library/Logs/DiagnosticReports/Codex-2026-06-27-*.ips. Full logs are not attached publicly because they may contain sensitive session data, but I can provide a redacted crash report if needed.