Hello OpenAI Support,
I encountered two reproducible crashes in the Codex Windows desktop app.
Environment:
- Microsoft Store package: OpenAI.Codex 26.721.4979.0
- Internal app build: 26.721.41059
- Windows version: 10.0.26200
- AMD Radeon 780M Graphics
- NVIDIA GeForce RTX 4050 Laptop GPU
- Virtual display drivers installed: Oray/Sunlogin, i4Remote, and Citrix
Reproduction steps:
- Start Codex.
- Let Browser Use open this JAMA Network page:
https://jamanetwork.com/journals/jamainternalmedicine/fullarticle/2833228
- After approximately 7–15 seconds, the entire Codex app exits.
- Codex cannot be opened again until Windows “Repair” is run for the application.
The issue occurred twice on July 29, 2026, at approximately 10:52 and 11:09 China Standard Time.
Both crashes ended with the same log messages:
“Recoverable Chromium child process gone exitCode=101457950 processType=GPU reason=crashed”
followed by:
“Recoverable Chromium child process gone exitCode=18 processType=GPU reason=launch-failed”
Windows did not record a system-level display-driver reset or a normal application crash dump. This appears to be an in-app browser/GPU compatibility issue, possibly involving hybrid or virtual display adapters. Codex should ideally recover from a GPU child-process crash instead of terminating the entire application.
Please investigate this compatibility issue and consider adding an official setting to disable hardware acceleration.
I can provide sanitized application logs if needed.
Thank you.
Codex-Windows-GPU-Crash-Evidence-2026-07-29.zip
Hello OpenAI Support,
I encountered two reproducible crashes in the Codex Windows desktop app.
Environment:
Reproduction steps:
https://jamanetwork.com/journals/jamainternalmedicine/fullarticle/2833228
The issue occurred twice on July 29, 2026, at approximately 10:52 and 11:09 China Standard Time.
Both crashes ended with the same log messages:
“Recoverable Chromium child process gone exitCode=101457950 processType=GPU reason=crashed”
followed by:
“Recoverable Chromium child process gone exitCode=18 processType=GPU reason=launch-failed”
Windows did not record a system-level display-driver reset or a normal application crash dump. This appears to be an in-app browser/GPU compatibility issue, possibly involving hybrid or virtual display adapters. Codex should ideally recover from a GPU child-process crash instead of terminating the entire application.
Please investigate this compatibility issue and consider adding an official setting to disable hardware acceleration.
I can provide sanitized application logs if needed.
Thank you.
Codex-Windows-GPU-Crash-Evidence-2026-07-29.zip