App crashes with V8 OOM in "git" worker thread during long computer-use sessions #34213

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

26.715.31925 (build 5551)

What subscription do you have?

Plus

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

App repeatedly crashes during long, goal-directed agentic tasks using the computer-use/testing feature. Happened 3 times so far, at roughly 87min, 71min, and 28min into separate sessions — duration varies but the pattern is consistent.

Root cause (confirmed from crash logs, not a guess): a V8 JavaScript heap out-of-memory in a Node worker thread named "git" that Codex spins up during these sessions. Node's own OOM handler catches it and calls abort():

abort()
→ node::OOMErrorHandler(char const*, v8::OOMDetails const&)
→ v8::ExternalMemoryAccounter::Update(...)

This looks like a memory leak in the git-integration worker that grows across a long session rather than a fixed timeout — the crash happens at different elapsed times but always in the same subsystem. One occurrence crashed while the app was backgrounded (not in focus), so it's not tied to active interaction either.

An earlier crash from the same setup (before this one) showed the same subsystem faulting via EXC_BREAKPOINT instead of SIGABRT — same root cause, different exit path, consistent with memory pressure building up differently each time.

In-app feedback already submitted, Feedback ID: no-active-thread-019f7ba0-0cb3-7282-80aa-966f2ddc7cdf

Full .ips crash logs available for both incidents, happy to attach.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019f7ba0-0cb3-7282-80aa-966f2ddc7cdf

What is the expected behavior?

The Codex app should remain stable during long computer-use/testing sessions, and the Git integration worker should release or bound memory instead of exhausting the V8 heap and terminating the app.

Additional information

No response