SafeDisk AI

Codex Crashpad Pending Dumps Taking Disk Space

If Codex Desktop keeps creating .dmp and _sidecar.json files under Crashpad, the disk growth can look like generic System Data. Measure the pending crash-report queue first, avoid sharing dump files publicly, and preserve app state before deleting anything broader.

Free browser cleanup

Find the biggest storage culprit first.

Run the Chrome or Edge web scan, delete one approved low-risk item free, then use the $29 Deep Cleanup only if meaningful space remains.

Start free cleanup Send $29 payment link
Read-only first pass

Measure both old and current Codex Crashpad paths.

These checks list counts, sizes, and time ranges. They do not read crash dump contents.

paths=(
  "$HOME/Library/Application Support/com.openai.codex/web/Crashpad"
  "$HOME/Library/Application Support/Codex/Crashpad"
)

for crash in "${paths[@]}"; do
  echo "== $crash =="
  [ -d "$crash" ] || { echo "missing"; continue; }
  du -sh "$crash" "$crash/pending" 2>/dev/null
  find "$crash/pending" -maxdepth 1 -type f 2>/dev/null | wc -l
  find "$crash/pending" -maxdepth 1 -type f -name '*.dmp' 2>/dev/null | wc -l
  find "$crash/pending" -maxdepth 1 -type f -name '*_sidecar.json' 2>/dev/null | wc -l
  find "$crash/pending" -maxdepth 1 -type f -print0 2>/dev/null \
    | xargs -0 stat -f '%Sm %z %N' -t '%Y-%m-%d %H:%M:%S' 2>/dev/null \
    | sort | sed -n '1p;$p'
done
Send $29 payment link

What Is Usually Safe To Remove?

Crashpad pending files are crash reports waiting to be processed or uploaded. They are usually recoverable disk space, but dump files may contain private memory, local paths, prompts, or project data. Do not attach .dmp files to a public issue.

  1. Quit Codex first.
  2. Confirm which Crashpad path is growing.
  3. Move only pending, new, completed, and attachments crash-report files to Trash.
  4. Restart Codex and watch whether the file count grows again.
  5. If it grows immediately, treat it as an active Crashpad loop, not a one-time cleanup.
Careful cleanup

Move Crashpad reports to Trash after Codex is stopped.

This does not delete conversations, projects, config, or the whole Codex app support folder.

osascript -e 'quit app "Codex"' 2>/dev/null || true
pkill -f "browser_crashpad_handler.*codex.*/Crashpad" 2>/dev/null || true

for crash in \
  "$HOME/Library/Application Support/com.openai.codex/web/Crashpad" \
  "$HOME/Library/Application Support/Codex/Crashpad"; do
  [ -d "$crash" ] || continue
  mkdir -p "$HOME/.Trash/SafeDisk-Codex-Crashpad"
  for bucket in pending new completed attachments; do
    [ -d "$crash/$bucket" ] || continue
    find "$crash/$bucket" -mindepth 1 -maxdepth 1 -exec mv {} "$HOME/.Trash/SafeDisk-Codex-Crashpad/" \;
  done
done
Send $29 payment link

Do Not Delete First

Need a second read before cleaning?

Use the free browser cleanup for local Mac storage, or request the $29 Deep Cleanup if the Crashpad queue, Codex app state, and System Data boundary are not obvious.

Start free cleanup Send $29 payment link
Deep Cleanup

Still full after the free cleanup?

Send your email once. We reply with the $29 payment link, one clarification, or a no-pay answer if the free cleanup is enough.

Start free cleanup first