Headroom Daily: Ghost Proxies, Routing Guards, and Freeze Recovery

Three linked proxy fixes dominate today's activity, ending weeks-long orphaned processes, blocking silent misrouting, and adding last-resort recovery from native freezes. Release 0.39.2 packages those fixes alongside Windows install and compression corrections.

Duration: PT2M23S

Episode overview

This episode is a short developer briefing from Headroom Daily.

It explains recent repository work in plain language.

  • Show: Headroom Daily
  • Published: 2026-09-28T22:00:05Z
  • Audio duration: PT2M23S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning, it's Monday, September 28th, 2026.

The lead story is proxy reliability. Three merged fixes trace back to one production incident where proxies lived 21 days after their sessions ended, holding ports and quietly hijacking later work.

First, orphan cleanup in pull request 3202. Wrap-spawned proxies are now marked as wrap-owned and run a background watchdog. If no live clients, no active socket sessions, and no recent request activity remain for a grace period, the proxy shuts itself down. Standalone and persistent installs are untouched.

Second, routing safety in pull request 3201. Wrap no longer reuses a running proxy with a different backend or upstream address. If that proxy is idle, it is restarted with the requested config. If clients are attached, wrap starts a dedicated proxy on a free port instead of disrupting them. That closes the case…

Third, freeze recovery in pull request 3180. A new hard watchdog handles native calls that seize the interpreter lock. Normal timeouts can't fire then, so after 90 seconds the process dumps every thread's stack to the log and exits. Supervised deployments restart cleanly instead of hanging forever.

In a second theme, small…

Nearby episodes from Headroom Daily

  1. Cache Misses and False Savings Fixes
  2. Emergency Proxy Rate Limit Fix Ships as 0.39.1
  3. Proxy Security and Fidelity Fixes
  4. Proxy Hardening, Compression Correctness, and Savings Clarity
  5. Cost Honesty and Fail-Closed Security
  6. Metrics Correction Ships in Point Release
  7. Fixing Inflated Savings Numbers
  8. Proxy Coexistence and Restart Reliability