Codex Desktop App Fills Disk Space with Continuous Crashpad Dumps on macOS

Unbounded Disk Usage by Codex Desktop

Users of the Codex Desktop application on macOS are experiencing significant disk space consumption due to continuous generation of Crashpad pending dumps. One user reported that the directory grew by 4.9GB and 54,504 files in a single day, with the count continuing to increase during investigation.

Application Remains Functional

Despite the rapid accumulation of crash dumps, the Codex Desktop application itself remains functional. Users can continue to use the app, inspect the filesystem, and interact with GitHub. This indicates that the problem is not a typical application crash, but rather an issue with how Crashpad handles and cleans up these diagnostic files.

Crashpad Dump Generation Issue

The core problem appears to be that Crashpad or a monitored helper process within the Codex app is repeatedly generating pending dump/sidecar pairs without proper bounding, upload/processing cleanup, or rotation. This leads to an ever-growing queue of diagnostic files that are not being managed, consuming multiple gigabytes of local storage daily.

Expected vs. Actual Behavior

Expected behavior for crash reporting systems like Crashpad includes bounding the number of reports, uploading/processing them, or rotating them to prevent excessive disk usage. The actual behavior observed in Codex Desktop is that pending Crashpad reports accumulate rapidly, leading to continuous disk space consumption.