3 people reported
All time, since Oct 5.
Memory extraction exhausts RAM
“The second shutdown was triggered by background memory extraction of an inactive, oversized chat.”
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/13256/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
Background memory extraction of large chat history exhausts RAM. The memory_stage1 job loads an old, oversized rollout into RAM and the backend is OOM-killed, without the chat being opened.
Is this your bug?
File my report- Where
- memory extraction
- Versions
- 0.162.0
- Platforms
- Linux, macOS
- How bad
- Stops work: a core feature can't be used.
Related: Desktop backend memory and process buildup
Not quite your bug?
- App-server memory balloons2 people
- Renderer OOM reloads desktop UI4 people
- Old images resent each request13 people
Original reports3, newest first
- [macOS Desktop] codex reaches 73.9 GB footprint during memory_stage1 extraction of a 26.3 GB historyOn GitHub#53842
- [Linux Desktop 26.1007] Background memory extraction of inactive 7 GiB chat OOMs native backend; no chat opening requiredOn GitHub#53039
- Automatic memory extraction OOMs on image-heavy rollouts and retries indefinitelyOn GitHub#51233