ChatGPT Windows browser-process crash immediately after in-app browser tab teardown
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.901.51231
What subscription do you have?
Pro
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
01a04e31-4d59-7020-8f1d-3fe266ecada6
Subject: ChatGPT Windows browser-process crash immediately after in-app browser tab teardown
ChatGPT Desktop repeatedly crashes while the active task “Build Eleva Rise Sales foundation” uses the in-app browser.
Five confirmed Electron browser-process crashes occurred at:
22:43 IST
07:49 IST
11:07 IST
12:31 IST
16:02 IST
Every crash occurred 0.6–1.1 seconds after an in-app browser tab teardown.
Latest sequence:
tabID=undefined
Crashpad crash ID:
719f2c90-a88e-4139-9588-b8eb3e58f214
Affected app versions:
26.901.5280.0
26.901.6511.0
The problem reproduces across both versions.
No corresponding GPU reset, resource-exhaustion event, Windows application hang, or updater termination was found.
The likely trigger is an invalid-state or race condition between:
- in-app browser tab teardown;
- picture-in-picture handling;
- browser-session cleanup.
Crashpad retained metadata but no minidump.
Please correlate the Crashpad ID and timestamps with native browser-process telemetry and advise whether additional desktop logs or a diagnostic build are required.
No ERP/site failure occurs at the same time.
What steps can reproduce the bug?
Feedback ID: 01a04e31-4d59-7020-8f1d-3fe266ecada6
What is the expected behavior?
No response
Additional information
Occured several times in the last 24 hours.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Start by correlating Crashpad ID 719f2c90-a88e-4139-9588-b8eb3e58f214 and the reported timestamps with native browser-process telemetry; done means determining whether the tab teardown, picture-in-picture handling, and browser-session cleanup are related and whether additional logs or a diagnostic build are required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100