What version of the Codex App are you using (From “About Codex” dialog)?
26.721.4979.0 x64 (Microsoft Store/MSIX)
What subscription do you have?
Unknown (consumer ChatGPT account)
What platform is your computer?
Windows x64 — Lenovo ThinkPad T490, Intel UHD Graphics 620, driver 31.0.101.2137
What issue are you seeing?
On Codex Desktop for Windows, opening https://app.dodopayments.com/ in the built-in browser causes the Chromium GPU child process to crash about 8 seconds after the page becomes DOM-ready. The GPU process then fails to relaunch. Codex exits, and relaunching may show a black or unusable window until all Codex processes are terminated.
The same URL works normally in regular Google Chrome. The problem still reproduces after updating the Intel UHD Graphics 620 driver from 30.0.101.1692 to 31.0.101.2137.
What steps can reproduce the bug?
- Open Codex Desktop on Windows.
- Open the built-in browser in a task.
- Navigate to https://app.dodopayments.com/.
- Wait approximately 8–10 seconds.
- Codex crashes. A subsequent launch may show a black window.
This is consistently reproducible in the Codex built-in browser, but not in regular Chrome.
What is the expected behavior?
The page should load in the built-in browser. If the embedded Chromium GPU child process fails, Codex should recover or disable acceleration for that webview instead of crashing or leaving the entire app black.
Additional information
Environment:
- Codex Desktop: 26.721.4979.0 x64 (Microsoft Store/MSIX)
- Device: Lenovo ThinkPad T490
- OS: Windows x64
- GPU: Intel UHD Graphics 620
- Active Intel GPU driver: 31.0.101.2137
- Also installed: MuMu Virtual Display Adapter
- External display: none
- The URL works normally in Google Chrome
Relevant log excerpt:
2026-07-26T02:43:44.681Z info [browser-sidebar-manager] browser sidebar dom-ready url=https://app.dodopayments.com/
2026-07-26T02:43:53.005Z warning Recoverable Chromium child process gone exitCode=101457950 processType=GPU reason=crashed serviceName=GPU
2026-07-26T02:43:53.020Z warning Recoverable Chromium child process gone exitCode=18 processType=GPU reason=launch-failed serviceName=GPU
The problem was first seen when restoring a task that had embedded browser tabs for Dodo Payments (and earlier, Render). After the crash, reopening the same task repeatedly triggered the failure. The crashing task was archived without reopening it.
Possibly related: #24904 and #24913, but this case has a consistent URL-specific trigger in the built-in browser.
What version of the Codex App are you using (From “About Codex” dialog)?
26.721.4979.0 x64 (Microsoft Store/MSIX)
What subscription do you have?
Unknown (consumer ChatGPT account)
What platform is your computer?
Windows x64 — Lenovo ThinkPad T490, Intel UHD Graphics 620, driver 31.0.101.2137
What issue are you seeing?
On Codex Desktop for Windows, opening https://app.dodopayments.com/ in the built-in browser causes the Chromium GPU child process to crash about 8 seconds after the page becomes DOM-ready. The GPU process then fails to relaunch. Codex exits, and relaunching may show a black or unusable window until all Codex processes are terminated.
The same URL works normally in regular Google Chrome. The problem still reproduces after updating the Intel UHD Graphics 620 driver from 30.0.101.1692 to 31.0.101.2137.
What steps can reproduce the bug?
This is consistently reproducible in the Codex built-in browser, but not in regular Chrome.
What is the expected behavior?
The page should load in the built-in browser. If the embedded Chromium GPU child process fails, Codex should recover or disable acceleration for that webview instead of crashing or leaving the entire app black.
Additional information
Environment:
Relevant log excerpt:
The problem was first seen when restoring a task that had embedded browser tabs for Dodo Payments (and earlier, Render). After the crash, reopening the same task repeatedly triggered the failure. The crashing task was archived without reopening it.
Possibly related: #24904 and #24913, but this case has a consistent URL-specific trigger in the built-in browser.