Codex Desktop crashes when Excalidraw opens a local image
Open 💬 2 comments Opened Jul 16, 2026 by Shadow-Xin
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Codex Desktop crashes when Excalidraw opens a local image
Codex version
26.707.91948
Platform
- macOS 26.5.1 (Build 25F80)
- Apple Silicon / arm64 (Apple M1)
- Electron/Chromium 150.0.7871.115
Issue
Codex Desktop exits completely when a local image is selected from Excalidraw in the built-in browser.
This is reproducible and appears to crash the embedded browser process rather than showing a normal page or renderer error.
Steps to reproduce
- Open the Codex built-in browser.
- Navigate to
https://www.excalidraw.com/. - Use Excalidraw's image/open function.
- Select a local image using the macOS file picker.
- Codex Desktop exits immediately.
Expected behavior
The selected image should be imported into Excalidraw. If the image cannot be decoded or local-file access is unsupported, the browser should display a recoverable error without terminating Codex Desktop.
Actual behavior
The entire Codex Desktop application exits.
Crash evidence
Two reproductions on July 16, 2026 generated pending Crashpad sidecars at approximately 15:04 and 15:09 local time:
{"osarch":"arm64","ptype":"browser"}
The files were created under:
~/Library/Application Support/Codex/Crashpad/pending/
No corresponding macOS DiagnosticReports crash file was generated.
Additional information
- The crash occurs through a user-driven local file picker inside the built-in browser.
- This may be related to local-file authorization, image decoding, or the embedded Chromium browser process.
- Related but less severe file-upload limitation: https://github.com/openai/codex/issues/20785
- No local image, image contents, account identifiers, or full telemetry logs are included in this report.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks! These issues appear related but not exact duplicates. #32683 is the closest because both crash the Chromium browser process, but mine occurs on macOS only after selecting a local image in an already working HTTPS page. #32773 involves direct file:// HTML navigation on Windows. I’ll keep this issue open unless maintainers confirm the same underlying crash signature.