Codex Desktop memory leak / Windows kernel memory retention

Resolved 💬 1 comment Opened Jun 28, 2026 by CudoMudo Closed Jun 28, 2026

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

Version 26.623.42026

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex Desktop memory leak / Windows kernel memory retention
Environment:
Windows 11
Codex Desktop app
Long-running coding sessions with local dev stack sometimes active
32 GB RAM
Observed behavior:
Over longer Codex Desktop sessions, system RAM climbs toward 98%.
Closing local dev stack and restarting Codex app does not fully release memory.
Task Manager does not show a normal user-process owner for the missing RAM.
RAMMap shows abnormal kernel memory usage:Page Table around 10 GB
Nonpaged Pool around 7 GB
Standby only around 670 MB
Unused around 7 GB

Without Codex usage, the machine does not show the same memory growth pattern.
Once this happens, RAM cannot be recovered without rebooting Windows.
Impact:
Long development sessions become impossible without reboot.
The issue is not solved by killing Laravel/Vite/MySQL/Redis/browser processes.
The memory appears retained at kernel/page-table/nonpaged-pool level after Codex-triggered workload.
Expected:
Closing/restarting Codex Desktop should release resources and not leave Windows with extreme Page Table / Nonpaged Pool growth.
Codex Desktop should avoid triggering unreclaimable kernel memory growth during long sessions.
Repro pattern:
Use Codex Desktop for an extended coding session.
Work with local project/dev environment and in-app browser.
Monitor RAMMap over time.
Page Table and Nonpaged Pool grow abnormally, eventually requiring Windows reboot.

What steps can reproduce the bug?

normal usage.

What is the expected behavior?

restarting app to release memory.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗