openai / openai/codex

Codex Windows 26.915.4065.0 repeatedly crashes in chrome.dll with 0xC0000005 (Crashpad ptype=browser)

Open
#46,644 1 comment 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

What version of the Codex App are you using (From “About Codex” dialog)?

26.915.4065.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

No response

What issue are you seeing?

Summary

Codex Desktop on Windows repeatedly crashes immediately after launch. The AppX package itself is healthy and the Codex sandbox service is running normally, but the main browser process crashes and generates Crashpad dump files every time.

Environment

  • OS: Windows 11 x64

  • Codex package:

    • Name: OpenAI.Codex
    • Version: 26.915.4065.0
    • PackageFullName: OpenAI.Codex_26.915.4065.0_x64__2p2nqsd0c76g0
    • Package status: Ok
  • Sandbox service:

    • Service: CodexSandboxService.OpenAI.Codex
    • Status: Running
    • StartType: Automatic

Crash behavior

Each time Codex is launched:

  1. The AppX container is created successfully.
  2. The Codex process starts.
  3. The main process exits/crashes shortly afterward.
  4. Crashpad generates a new .dmp and _sidecar.json.
  5. The application closes unexpectedly.

The Crashpad sidecar contains:

{"capture_kind":"crash","osarch":"x86_64","ptype":"browser"}

This indicates that the crashing process is the browser/main process.

Dump analysis

The latest dump shows:

Exception code: 0xC0000005
Exception type: Access Violation

Faulting module:
chrome.dll

Module path:
C:\Program Files\WindowsApps\OpenAI.Codex_26.915.4065.0_x64__2p2nqsd0c76g0\app\chrome.dll

The crash occurs inside Codex's bundled Chromium chrome.dll.

Crashpad reports

New dump files are generated on every failed launch, for example:

94d5fcdf-3d64-4ac5-860c-9f7bfbdc4dbd.dmp
94d5fcdf-3d64-4ac5-860c-9f7bfbdc4dbd_sidecar.json

d26fc384-8c41-4e15-963f-0228e1a17314.dmp
d26fc384-8c41-4e15-963f-0228e1a17314_sidecar.json

AppX / service state

The Codex AppX package currently reports:

Name            : OpenAI.Codex
PackageFullName : OpenAI.Codex_26.915.4065.0_x64__2p2nqsd0c76g0
Version         : 26.915.4065.0
Status          : Ok

The sandbox service reports:

Status      : Running
Name        : CodexSandboxService.OpenAI.Codex
DisplayName : ChatGPT
StartType   : Automatic

Therefore the current failure does not appear to be caused by the sandbox service being unavailable.

Previous AppX update errors

During an earlier Codex package update/repair attempt, Windows logged several AppX deployment errors, including:

0x80073D02
Unable to install because OpenAI.Codex was still running.

0x80073CF1
Package registration/state repair failed because the package could not be found in the repository.

0x80073CF0
Failed to open AppxManifest.xml because the path could not be found.

0x80073D28
Administrator privileges were required to install/register the packaged service.

However, Windows later successfully re-registered the Codex package, and the current package status is Ok.

Troubleshooting already performed

The following have already been tested:

  • Restarted Windows.

  • Verified AppX package status is Ok.

  • Verified CodexSandboxService.OpenAI.Codex is running.

  • Checked Windows Application Error / Windows Error Reporting logs.

  • Checked WebView2 runtime.

  • No corresponding WebView2 crash was found.

  • Tested with Chromium GPU disabled:

    • --disable-gpu
  • Disabled virtual display driver:

    • OrayIddDriver Device
  • Disabled display/GPU related devices for testing.

  • Verified the crash still occurs.

  • Crashpad continues to generate new dumps.

  • The Crashpad process type remains:

    • ptype=browser

Graphics environment

Detected display adapters included:

OrayIddDriver Device
AMD Radeon 780M Graphics

The virtual display driver was disabled during testing, but the Codex crash continued.

Expected behavior

Codex should start normally and remain open.

Actual behavior

Codex launches, the main Chromium/browser process crashes with 0xC0000005 inside chrome.dll, and the application exits.

Additional files available

I can provide:

  • Latest Crashpad .dmp
  • Corresponding _sidecar.json
  • AppX deployment logs
  • Windows Event Viewer logs
  • AppX package/service status output

Latest sidecar:

{"capture_kind":"crash","osarch":"x86_64","ptype":"browser"}

Please let me know if a full minidump or additional diagnostic logs are needed.

00ffe9b6-f5cf-452d-9f3e-a90ab653045e.dmp
00ffe9b6-f5cf-452d-9f3e-a90ab653045e_sidecar.json

What steps can reproduce the bug?
  1. Launch the Codex Desktop app on Windows.
  2. Wait a few seconds after the main window appears.
  3. The app crashes and closes automatically.
  4. Launch Codex again.
  5. The same crash happens again.

A new Crashpad dump file is generated after each crash.

This reproduces consistently on Codex version 26.915.4065.0.

What is the expected behavior?

No response

Additional information

No response

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 by reproducing the launch crash on Windows with Codex 26.915.4065.0, then inspect the attached Crashpad .dmp and _sidecar.json alongside the Windows Application Error and deployment logs. Completion means the browser process no longer crashes and Codex remains open after launch.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.