Windows x64 ChatGPT/Codex 26.707.9981.0: repeated 0xC06D007F and 2-3 second system input lag when opening a new task

Open
#33,438 9 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust

Research direction

Start by reproducing the new-task sequence on Windows 11 and correlate the Application Error event with dumps in %LOCALAPPDATA%\CrashDumps. Compare the fresh logs_2.sqlite and reduced .codex\sessions setup against the related reports; done means no repeated 0xc06d007f event, crash dump, or system input lag.

Written by the indexing model from the issue text.

Description

app bug performance windows-os

App and system

  • App package: OpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0
  • Package status: Ok
  • OS: Windows 11 Pro, version/build 10.0.26200
  • Architecture: x64 / 64-bit
  • CPU: 11th Gen Intel Core i7-1185G7
  • RAM: 31.7 GB
  • GPU: Intel Iris Xe Graphics, driver 32.0.101.7077

Problem

Every time I open a new task, the task pane is initially blank for roughly 2-3 seconds. During that interval, the mouse pointer becomes extremely heavy and delayed, as if the entire input path is stalling. The task content then appears and pointer movement returns to normal.

Windows records an Application Error event for ChatGPT.exe during the same operation, and Windows creates a new crash dump. The app often remains open despite the event.

The repeated event signature is:

Faulting application: ChatGPT.exe
Faulting module: unknown
Exception code: 0xc06d007f
Application path: C:\Program Files\WindowsApps\OpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0\app\ChatGPT.exe

The dumps are approximately 10-11 MB each and are written under %LOCALAPPDATA%\CrashDumps.

Reproduction

  1. Start ChatGPT/Codex on Windows.
  2. Create or open a new local Codex task.
  3. Move the mouse while the new task pane is loading.
  4. Observe severe pointer/input lag for about 2-3 seconds while the pane is blank.
  5. Check Windows Application events and %LOCALAPPDATA%\CrashDumps.
  6. A new ChatGPT.exe event with exception 0xc06d007f and a corresponding dump are created.

This reproduces repeatedly, including with a newly created task.

Troubleshooting already performed

  • Microsoft Store reported no newer build.
  • Ran Windows Package Manager repair successfully. It repaired the same 26.707.9981.0 package; the error resumed immediately.
  • Completely uninstalled and reinstalled the Store package. Windows created a brand-new package-state directory. The same exception resumed on the fresh installation.
  • Disabled Browser full CDP/developer access.
  • Rotated logs_2.sqlite and allowed Codex to create a fresh log database. The old database was about 132 MB; behavior was unchanged with a fresh database.
  • Reduced the active .codex\sessions hot path from 76 JSONL files totaling about 151.9 MB to one current session file totaling about 4.1 MB. Behavior was unchanged, and the same exception continued.
  • PB Books/project files, memories, skills, authentication, and configuration were not involved in these tests.

On the one-session test, two identical 0xc06d007f events appeared within the first minute after restart.

Expected behavior

Creating or opening a task should not stall system mouse/input handling, and ChatGPT.exe should not generate an Application Error event and crash dump for each operation.

Related reports

  • #28855 - Windows system mouse/input lag
  • #29543 - 2-3 second freeze during first input in every new conversation
  • #28109 - session-directory scanning and brief input freezes
  • #33045 - Windows x64 performance regression in the unified 26.707 app
  • #33381 - same package build and 0xc06d007f on ARM64; this report is x64 and may have a different failing native module

Diagnostics and privacy

I have retained the minidumps and a screen recording locally. I am not attaching raw dumps publicly because minidumps may contain process memory, but I can provide them privately to an OpenAI maintainer or support channel.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

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.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.