Codex Windows app crashes after the in-app browser GPU process fails

Open 💬 2 comments Opened Jul 29, 2026 by fineshe
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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:

  1. Start Codex.
  2. Let Browser Use open this JAMA Network page:

https://jamanetwork.com/journals/jamainternalmedicine/fullarticle/2833228

  1. After approximately 7–15 seconds, the entire Codex app exits.
  2. 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

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #35891
  • #35635
  • #35411
  • #35352
  • #35505

Powered by Codex Action

fineshe · 1 month ago

Confirmed as a duplicate of #35352 after checking Windows Code Integrity Event ID 3033. I have added the additional reproduction evidence to #35352. Closing this issue in favor of the main tracking issue.