Bug: Codex WSL process crashes and generates very large crash dumps in Windows Temp

Bug: Codex WSL process crashes and generates very large crash dumps in Windows Temp

Environment:

• Windows
• Codex running through WSL
• Codex installation/runtime located under E:\codex
• WSL crash dumps are written to:
  C:\Users\Administrator\AppData\Local\Temp\wsl-crashes

Issue:

While using Codex, I noticed that my C: drive was being written to heavily and unexpectedly losing free disk space.

After investigating Windows Temp, I found multiple WSL crash dumps. In particular, processes launched from the Codex WSL runtime appear to have crashed:

wsl-crash-1789140886-80554-_mnt_e_codex_bin_wsl_1a4f6f66dd2f3710_rg-7.dmp
Size: 1.685 GB

wsl-crash-1789140886-83188-_mnt_e_codex_bin_wsl_1a4f6f66dd2f3710_rg-7.dmp
Size: 0.212 GB

Both filenames point to the rg (ripgrep) executable under the Codex WSL runtime.

Other WSL processes have also produced crash dumps in the same directory, including:

• Python 3.13: 1.359 GB
• dockerd: 0.221 GB
• systemd-logind
• cron

The main concern is that Codex-related rg crashes can generate extremely large dump files in %LOCALAPPDATA%\Temp\wsl-crashes. If the crash happens repeatedly, these dumps can rapidly consume many GB of the Windows system drive.

Expected behavior:

• Codex/rg should not crash during normal repository search.
• A crash should not repeatedly generate multi-GB dump files capable of filling the Windows C: drive.
• Ideally Codex should detect/recover from the failing WSL subprocess and prevent unbounded crash-dump accumulation.

Observed behavior:

• Codex-related rg process crashed at least twice.
• One crash generated a 1.685 GB .dmp.
• Windows C: drive experienced heavy unexpected writes.
• The crash dumps accumulated under the Windows user Temp directory.

Please investigate whether the Codex WSL-bundled rg process or its WSL execution environment can trigger these crashes and whether crash dump generation can be bounded or cleaned automatically.

No source file or failing test is named. Start by reproducing the WSL rg crash from the Codex runtime under E:\codex and inspect the resulting files in %LOCALAPPDATA%\Temp\wsl-crashes. Done means identifying the crash path and defining bounded dump growth or cleanup and reliable subprocess recovery.