Updated Codex Always Crash!!!

Open 💬 5 comments Opened Jun 3, 2026 by YookiTong

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

26.601.21317 (build 3511) Also reproduced on 26.527.60818 (build 3437).

What subscription do you have?

Pro plan ($200/mo) 20x more usage than Plus, GPT-5.5 Pro

What platform is your computer?

_No response_

What issue are you seeing?

Title:
Codex Desktop repeatedly crashes: git worker triggers Node/V8 OOM and aborts process

Environment:

App: Codex Desktop
Bundle ID: com.openai.codex
Hardware: Mac16,7, Apple M4 Pro, 24GB unified memory
OS: macOS 26.3.1 (25D2128)
Crash type: EXC_CRASH
Termination: SIGNAL code=6 / SIGABRT
Triggered thread: git
Common stack evidence: node::OOMErrorHandler(...)
Pattern: 12 recent crash reports all show triggered_thread=git and node_oom=True

Representative crashed thread stack from latest report:
Thread name: git
Triggered: true

app_name: Codex
timestamp: 2026-06-02 16:37:01.00 +0800
app_version: 26.527.60818
build_version: 3437
bundleID: com.openai.codex
procPath: /Applications/Codex.app/Contents/MacOS/Codex
modelCode: Mac16,7
osVersion: macOS 26.3.1 (25D2128)
incident: C0555175-7433-4D63-93AC-269FB4D4A9A4

exception:
type: EXC_CRASH
signal: SIGABRT

termination:
namespace: SIGNAL
code: 6
indicator: Abort trap: 6
byProc: Codex
byPid: 42508

legacyInfo:
threadTriggered:
name: git

TRIGGERED THREAD
id: 147863605 name: git triggered: True

00 __pthread_kill + 8 [libsystem_kernel.dylib]
01 pthread_kill + 296 [libsystem_pthread.dylib]
02 abort + 124 [libsystem_c.dylib]
03 node::OOMErrorHandler(char const*, v8::OOMDetails const&) + 344 [Codex Framework]
04 v8::ToExternalPointerTag(unsigned short) + 468 [Codex Framework]
05 v8::ToExternalPointerTag(unsigned short) + 352 [Codex Framework]
06 v8::ExternalMemoryAccounter::Update(v8::Isolate*, long long) + 39756 [Codex Framework]
07 cppgc::internal::WriteBarrier::DijkstraMarkingBarrierSlow(void const*) + 79252 [Codex Framework]
08 cppgc::internal::WriteBarrier::DijkstraMarkingBarrierSlow(void const*) + 74696 [Codex Framework]
09 cppgc::internal::WriteBarrier::DijkstraMarkingBarrierSlow(void const*) + 73400 [Codex Framework]
21 v8::internal::compiler::CompilationDependencies::DependOnElementsKind(...) + 83648 [Codex Framework]
22 v8::internal::ThreadIsolation::LookupJitAllocation(...) + 5832 [Codex Framework]
23 v8_inspector::V8ContextInfo::executionContextId(...) + 49392 [Codex Framework]
24 node::InternalCallbackScope::Close() + 412 [Codex Framework]
25 node::InternalMakeCallback(...) + 464 [Codex Framework]
26 node::AsyncWrap::MakeCallback(...) + 280 [Codex Framework]
27 node::HandleWrap::OnClose(uv_handle_s*) + 496 [Codex Framework]
28 uv_run + 528 [Codex Framework]
29 node::SpinEventLoopInternal(node::Environment*) + 464 [Codex Framework]
30 node::worker::Worker::Run() + 4848 [Codex Framework]
31 node::worker::Worker::SelfSize() const + 132 [Codex Framework]
32 _pthread_start + 136 [libsystem_pthread.dylib]
33 thread_start + 8 [libsystem_pthread.dylib]

0 __pthread_kill
1 pthread_kill
2 abort
3 node::OOMErrorHandler(char const*, v8::OOMDetails const&)
4 v8::ToExternalPointerTag(unsigned short)
5 v8::ToExternalPointerTag(unsigned short)
6 v8::internal::OptimizingCompileTaskExecutor::RunCompilationJob(...)
7 v8::internal::ThreadIsolation::JitPageReference::AllocationContaining(...)
8 v8::internal::ThreadIsolation::JitPageReference::AllocationContaining(...)
9 v8::internal::ThreadIsolation::JitPageReference::AllocationContaining(...)

Impact:
Codex Desktop repeatedly exits unexpectedly during normal use. The crash reports are consistent across multiple versions, and all point to a git worker thread aborting after Node/V8 OOM handling.

Expected:
A git/background worker OOM should not terminate the entire desktop app. Ideally the worker should fail/restart gracefully, or the app should bound git/file scanning memory usage.

Actual:
The Codex process receives SIGABRT from the git worker after node::OOMErrorHandler, causing the entire desktop app to crash.

What steps can reproduce the bug?

it seems some git memory leakage

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

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