8 people reported
All time, since Sep 27, including 2 thumbs-up on GitHub.
Runaway Git processes exhaust memory
“The instruction at 0x00007FFD9C2BB2C0 referenced memory at 0x0000000000000000. The memory could not be written.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/9272/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Codex spawns thousands of Git processes, exhausting Windows system memory. Git and console-host (conhost.exe) processes accumulate until system commit runs out, followed by git.exe crashes and other Windows processes failing.
Is this your bug?
File my report- Where
- Windows desktop app
- Error text
The instruction at 0x00007FFD9C2BB2C0 referenced memory at 0x0000000000000000. The memory could not be written.- Versions
- 2.53.0 to 26.1013.31256
- Platforms
- Windows
- How bad
- Stops work: a core feature can't be used.
Related: Desktop backend memory and process buildup
Not quite your bug?
- Canceled Git diffs stay running2 people
- Git console error windows4 people
- Turn-diff tmp_pack files fill disk3 people
Original reports6, newest first
- [Windows] Codex-descended Git storms (5,023 / 1,132 processes), commit exhaustion and LSM failureOn GitHub#55753
- Windows desktop: 5,737 concurrent Git processes exhaust system commit and crash appOn GitHub#54497
- Windows: Codex app-server spawns thousands of Git processes and exhausts system commitOn GitHub#53645
- Windows: runaway Git processes exhaust system memoryOn GitHub#53063
- [Windows Desktop 26.1002 / mobile Remote] opening Remote coincides with 6,094 Codex-descended Git processes and system commit exhaustionOn GitHub#52574
- Windows desktop 26.924.2738.0: recurring accumulation of Git processes, 98% physical RAM and severe system slowdownOn GitHub#48666