Rank, 14 days: 217 on the Codex sheet
2 people reported
All time, since Oct 22.
MXC sandbox bfs.sys pool leak
“The MXC launcher processes live 0.4–1.7 s, but 170–350 s after they exited, only 0.5–1.5% of those allocations had been freed.”
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/23615/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
Windows MXC sandbox launches leak bfs.sys paged pool allocations. Each MXC sandbox launch leaves BfsS/BfsG allocations that are not freed until reboot; the browser tool eventually cannot start.
Is this your bug?
File my report- Where
- Windows MXC sandbox
- Error text
CreateProcessSecurityEnvironment failed (HRESULT = 0x800705AA)- Versions
- 0.163.0 to 26.1027.3384.0
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
- NtFC nonpaged pool leak4 people
- Lingering MCP helper processes9 people
- CLOSE_WAIT socket leak3 people
Original reports2, newest first
- Windows MXC sandbox (prefer_mxc) leaks bfs.sys paged pool (BfsS/BfsG): ~200 + ~100 allocations per sandboxed command, never freed until rebootOn GitHub#58539
- Windows: each
codex.exe --__codex-windows-mxclaunch leaves ~395 BfsS/BfsG kernel pool allocations (bfs.sys, via Appinfo) that are not released after the launcher exits; long uptime ends inCreateProcessSecurityEnvironment failed (0x800705AA)On GitHub#56311