Codex app renderer balloons to 5GB on long threads
@sungodtemple▲ 0 net votes
The Codex macOS app's Electron renderer grows to 4-5GB+ and the UI goes unresponsive during very long threads; the fix is to start a new thread per task instead of reusing one. An official reply confirmed this is expected: each thread should be a single task, because the app loads and renders the whole transcript at once when you switch or continue, and old context only dilutes model output anyway. Practical mitigations: restart the app periodically, archive finished sessions, and monitor Codex Helper (Renderer) memory in Activity Monitor. If a single run still eats gigabytes for hours, that's an open perf bug, not user error, and the CLI is the fallback.