App-server memory balloons

“The affected process has the app-server argument; it is not an MCP child or the renderer.”

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/9661/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

Bundled app-server memory grows to tens of GiB. The desktop app's bundled codex app-server process balloons in resident memory, causing heavy swap on macOS or a global OOM kill on Linux.

Is this your bug?

File my report

Where: desktop app-server
Error text: Out of memory: Killed process 3716904 (codex) total-vm:70952576kB, anon-rss:46741212kB, file-rss:896kB, shmem-rss:0kB, UID:1000 pgtables:113180kB oom_score_adj:100
Versions: 0.162.0-alpha.2
Platforms: Linux, macOS
How bad: Stops work: a core feature can't be used.

Part of: Desktop backend memory and process buildup3 bugs

Lingering MCP helper processes9 people
Helper processes accumulate4 people

Not quite your bug?

Memory extraction exhausts RAM3 people

Original reports2, newest first

Oct 8, 2026[macOS][app-server 0.162.0-alpha.2] Footprint grows from 8.1G to 20G shortly after launch, with 24.4G peak and severe swap activityOn GitHub#52343
Oct 8, 2026[Linux Desktop] Bundled app-server reaches 44.6 GiB RSS and triggers global OOM with two long-running threadsOn GitHub#51947