4 people reported

All time, since Oct 6, including 1 thumbs-up on GitHub.

Startup crash from queued images

“Codex Desktop repeatedly closes during image-based work and can subsequently fail to stay open.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/10474/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports and thumbs-up in the last two weeks, down from 3 a week at the early-October peak. A workaround is known.

Desktop app crashes at startup from oversized queued image attachments. .codex-global-state.json grows to hundreds of MB from inline image data URLs persisted in queued-follow-ups.

Is this your bug?

File my report
Where
Desktop app
Error text
FAILURE_BUCKET_ID: BREAKPOINT_80000003_chrome.dll!Unknown
Versions
26.930.21537
Platforms
macOS, Windows

Not quite your bug?

  1. Old images resent each request13 people
  2. Desktop app crashes at startup7 people
  3. Memory extraction exhausts RAM3 people

Original reports3, newest first

  1. [Windows] Desktop exits on startup with chrome.dll 0x80000003 after large image attachments persist in queued-follow-upsOn GitHub#52912
  2. Oversized GIF in saved message queue causes startup crash loopOn GitHub#51818
  3. [Windows app] Large queued PNG attachments inflate global state to 140–191 MB; repeated exits and startup failureOn GitHub#51261

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.