openai / openai/codex

[Windows] Desktop 26.903.8094.0 crashes while idle at startup (browser then renderer)

Open
#44,115 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Summary

Codex desktop crashes on Windows while idle immediately after startup. No task was started or running during the reproduction.

Updating the Microsoft Store package from 26.901.6511.0 to 26.903.8094.0 did not resolve it.

Environment

  • OS: Windows 11 Home, build 26100, x64
  • Desktop package: OpenAI.Codex_26.903.8094.0_x64__2p2nqsd0c76g0
  • Crashpad reports: capture_kind=crash, osarch=x86_64

Minimal reproduction observed

  1. Update Codex desktop from 26.901.6511.0 to 26.903.8094.0 using Microsoft Store.
  2. Start Codex desktop and do not begin a task.
  3. The application crashes/restarts during idle startup.

Local timestamps, UTC+08:00, on 2026-09-09:

  • 17:50:48: Crashpad sidecar 7da4d5ce-6e6a-4295-bf68-aef4eb39df3e, ptype=browser
  • 17:50:53: a replacement desktop main process starts
  • 17:51:06: Crashpad sidecar a495b518-49e8-48dc-86aa-ba2a24f048ba, ptype=renderer

The prior package also crashed before the update (17:46:11, ptype=renderer), so this report does not claim the upgrade introduced the defect. It shows that the upgrade did not resolve it.

Expected behavior

The desktop client should remain open and usable when idle after startup.

Actual behavior

The browser process crashes, the desktop application relaunches, and then a renderer process also crashes before any task is started.

What has not been done

  • No chat database, cache, or local state was cleared or rebuilt.
  • No task content, personal paths, or full logs are attached.
  • The in-app browser/browser-use feature was disabled before this reproduction.

The available Crashpad sidecars only identify the crashed process type; they do not include a stack trace that can be safely attached here.

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

No source file or test is named. Start by reproducing the idle-startup crash on Windows 11 with the listed package versions and inspect the Crashpad browser and renderer reports; done means the desktop remains open and usable while idle after startup without either process crashing.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.