openai / openai/codex

Windows desktop 26.903.8094.0: browser-process crash during remote work, shortly after IAB tab cleanup

Open
#44,340 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug remote windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Environment

Windows x64; Microsoft Store package OpenAI.Codex 26.903.8094.0 (display name ChatGPT).

Problem

The app exited during remote work and the host became unreachable through the app. The laptop lid had been closed; whether this caused the crash is unknown. The app was reopened about three minutes later.

Evidence
  • Main app log stopped at 2026-09-09 23:41:24.676 UTC.
  • A Crashpad sidecar was written about one second later with capture_kind=crash, osarch=x86_64, ptype=browser.
  • The last events involved disposal and closure of an IAB browser sidebar tab, followed by runtime dependency diagnosis completing with installed=true and problemCount=0.
  • No sleep or reboot event was found near the interruption. Both AC and battery lid actions were set to do nothing.
  • Reopening did not change the package version.
Expected

An awake host remains reachable, and disposing an internal browser tab does not terminate the app.

Limitations

This is one incident without a confirmed reproduction sequence or crash stack. The browser cleanup and lid closure are correlations, not established causes.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the main app log ending at 2026-09-09 23:41:24.676 UTC and the Crashpad sidecar showing ptype=browser, then correlate the IAB tab disposal events with the runtime dependency diagnosis. Done means establishing a reproducible trigger or an actionable crash diagnosis; the report currently provides neither a stack nor a reproduction sequence.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.