Codex Crash Handler Loop Fills Disk With Unbounded Dumps

Codex Desktop’s crash reporting system is continuously generating dump files without bounds, accumulating 4.9GB in a single day in one report and reaching 61GB in another. The Crashpad pending directory grows at rates exceeding one crash report per second, filling disk with hundreds of thousands of paired .dmp and .json sidecar files while the app itself remains functional.

The root cause is a crash loop in the browser_crashpad_handler process. Each handler crash generates dump files before restarting, then fails again with mach_port_request_notification errors, perpetuating the cycle indefinitely. The failures originate in the exception handler server and appear tied to browser functionality, though disabling related features doesn’t stop the accumulation.

This creates two critical issues: rapid disk exhaustion that can render systems unusable, and privacy exposure since crash dumps contain memory snapshots and file paths. The problem persists across multiple Codex versions and survives reinstalls and app restarts.