NtFC nonpaged pool leak

“Running Codex Desktop over a period of time causes a severe system-wide kernel memory leak.”

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

Growing. 1 report in the last 7 days and none the week before, down from 2 a week at the late-October peak. A workaround is known.

Windows NtFC nonpaged pool leak while Codex runs. Nonpaged pool memory stays allocated after exiting the app until reboot, causing system stuttering, out of memory behavior and freezes.

Is this your bug?

File my report

Where: Codex desktop app
Versions: 26.908.4834.0 to 26.1027.3384.0
Platforms: Windows
How bad: Stops work: a core feature can't be used. Some reports say it used to work.

Not quite your bug?

MXC sandbox bfs.sys pool leak2 people
Runaway Git processes exhaust memory8 people
CLOSE_WAIT socket leak3 people

Original reports4, newest first

Nov 1, 2026Windows 26H1: deterministic NtFC nonpaged-pool leak through AppData junctions in Codex 26.1027.3384.0On GitHub#58641
Oct 22, 2026Windows MSIX desktop app leaks kernel nonpaged pool (NtFC) at 150–212 MB/min — 32 GB RAM exhausted in ~2 hoursOn GitHub#56160
Oct 21, 2026Severe Kernel Nonpaged Pool Memory Leak (Tag: NtFc) triggered by Codex DesktopOn GitHub#55812
Sep 16, 2026[Windows][26.908.4834.0] Severe NtFC nonpaged pool leak — several GB remain allocated until rebootOn GitHub#45947