3 people reported

All time, since Oct 13, including 1 thumbs-up on GitHub.

CLOSE_WAIT socket leak

“After that restart, a query-only observation of the exact backend identity found 204 initial CLOSE_WAIT connections.”

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

Desktop backend leaks TCP sockets stuck in CLOSE_WAIT on Windows. The app-server process "never closes TCP connections to the ChatGPT backend"; counts grow over long sessions, with UI stalls reported.

Is this your bug?

File my report
Where
Desktop app-server
Versions
26.1013.3656.0
Platforms
Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Lingering MCP helper processes9 people
  2. Desktop requests expire queued after RPC stalls fill in-flight slots4 people
  3. Desktop app browser-process crash3 people

Original reports2, newest first

  1. [Windows Desktop 26.1013.3656] codex app-server leaks chatgpt.com TCP sockets in CLOSE_WAIT (~1,500 in 14 h, ~200-350/h)On GitHub#54696
  2. Codex Desktop on Windows: persistent backend CLOSE_WAIT and intermittent UI stalls; request for supported aggregate diagnosticsOn GitHub#53667

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.