- Published on
Codex Desktop continuously generates Crashpad pending dumps
- Authors

- Name
- DeepHorus
Codex Desktop on macOS is continuously generating Crashpad pending dumps, causing unbounded local disk growth. One user reported the directory grew to 4.9GB and 54,504 files in a single day. The app remained functional during the incident, so the problem is not a full application crash.
The issue, #25921, describes paired .dmp and _sidecar.json files under ~/Library/Application Support/com.openai.codex/web/Crashpad/pending. Measurements showed 27,252 .dmp files and 27,252 _sidecar.json files. During the investigation, the count increased from 53,444 to 54,064, then to 54,504, indicating active generation.
The affected environment includes Codex Desktop app version 26.527.60818 with CFBundleVersion 3437. The machine runs macOS 26.3.1 (25D771280a) on arm64 architecture. Live process annotations show prod=Codex_Mac and ver=148.0.7778.179.
Two browser_crashpad_handler processes have run under PPID=1 since Sat May 30 11:47:50 2026. Both use the same Crashpad database located in the user's Application Support folder. The local app stayed usable enough to inspect and report the issue.
Expected behavior is that crash reports should be bounded, uploaded, processed, rotated, or not continuously generated while the app remains usable. Actual behavior shows pending Crashpad reports accumulate rapidly and consume multiple gigabytes of local disk space. The user did not attach minidumps publicly because they may contain memory, local paths, or private data.
The user can share the newest .dmp privately if OpenAI maintainers provide a safe upload path. Related issues include #25259, a stale Crashpad helper after an update, and #11090, orphaned Codex processes and UI freezes. Another prior report, #10627, covered Crashpad and macOS startup problems.
Until OpenAI addresses cleanup, rotation, or upload, users may face multi-gigabyte disk consumption. The issue highlights a background crash-handling bug in Codex Desktop. A fix should prevent unbounded pending dump generation while preserving crash diagnostics.