[Windows Desktop 26.707.12708.0] Severe lag while typing and switching tasks; repeated 0xc06d007f crashes

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #33541
• #33518
• #33375
• #33529
• #33494

Powered by Codex Action

Confirmed on the exact same Microsoft Store package: OpenAI.Codex_26.707.12708.0_x64__2p2nqsd0c76g0.

Fresh-process evidence from a controlled restart:

• main ChatGPT.exe process started at 17:53:36 local time
• first matching Application Error event appeared at 17:53:54 (18 seconds later)
• that same process accumulated 18 Event ID 1000 records through 18:04:06
• every one used exception code 0xc06d007f
• across the full day, Event Viewer contained 740 matching ChatGPT.exe Event ID 1000 records, all with 0xc06d007f
• desktop logs contained 39 ResizeObserver loop completed with undelivered notifications entries for the fresh process, and 1,045 for the day

The task-switch pass also showed 29 Git repo-watcher starts and 20 local Git state probes, but zero git pull or git fetch commands. One local Git operation was delayed for 5.6 seconds while desktop background requests were also slow (plugin/list up to 10.5 seconds and mcpServerStatus/list 22.2 seconds). This makes the Git failures look like a downstream symptom rather than a remote Git/network cause.

The same machine also independently reproduces the MCP lifecycle defect in #33531. Cleaning retained MCP children noticeably reduces lag, but it does not stop the 0xc06d007f events or renderer errors. The two defects appear to coexist and compound the UI latency.

No raw logs, task contents, usernames, credentials, or absolute paths are included.

I can confirm this issue on Windows 11 26H1 (build 28000.2525), x64, with Codex 26.707.12708.0. At the time of diagnosis, Event Viewer retained 451 identical ChatGPT.exe Application Error event ID 1000 records with exception code 0xc06d007f: 182 under the previous 26.707.9981.0 package and 269 under 26.707.12708.0. The current package produced its first identical failure approximately 11 seconds after its first launch, and during one controlled reproduction four matching events were recorded within 15 seconds.

Static inspection of the shipped package points to the bundled Codex Micro/Work Louder integration. codex-micro-service loads @worklouder/device-kit-oai, whose node-hid HID.node delay-imports 61 Node/N-API procedures through node.exe, including napi_create_function. ChatGPT.exe exports none of those N-API procedures, while the bundled chrome.dll exports all of them. The renderer’s Codex Micro bridge calls getState() and updateLighting() on the same task-state transitions that reproduce the stalls: sending a message, switching tasks, and response finalization. If the lazy service import fails, its promise is cleared, allowing subsequent state changes to retry the same native-module load.

I have not captured the live DelayLoadInfo structure, so the exact missing export is not independently confirmed on my x64 system. However, the exception code, binary imports, application code path, timing correlation, and repeated WER events strongly indicate the same native-module delay-load failure family reported in #33570. A fixed build should rebuild the native addon for the bundled Electron version; until then, disabling the Codex Micro feature gate or providing a user-accessible switch would prevent the repeated failures.

Unusable in windows, crashing every 2 mins

<img width="1042" height="251" alt="Image" src="https://github.com/user-attachments/assets/8ea6ab08-4c7e-46e4-a75f-d5ecf8afe48e" />

Log Name: Application
Source: Application Hang
Date: 17-07-2026 10:53:52
Event ID: 1002
Task Category: Hanging Events
Level: Error
Keywords:
User: SYSTEM
Computer: Datta-Home
Description:
The program ChatGPT.exe version 150.0.7871.124 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" Guid="{c631c3dc-c676-59e4-2db3-5c0af00f9675}" />
<EventID>1002</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>101</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2026-07-17T05:23:52.1107572Z" />
<EventRecordID>192731</EventRecordID>
<Correlation />
<Execution ProcessID="12316" ThreadID="21084" />
<Channel>Application</Channel>
<Computer>Datta-Home</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AppName">ChatGPT.exe</Data>
<Data Name="AppVersion">150.0.7871.124</Data>
<Data Name="ProcessId">0x2030</Data>
<Data Name="StartTime">0x1dd15ac6be7e34d</Data>
<Data Name="TerminationTime">4294967295</Data>
<Data Name="ExeFileName">C:\Program Files\WindowsApps\OpenAI.Codex_26.715.2305.0_x64__2p2nqsd0c76g0\app\ChatGPT.exe</Data>
<Data Name="ReportId">ce8c3d3a-0d66-4e85-9d18-896ed4634696</Data>
<Data Name="PackageFullName">OpenAI.Codex_26.715.2305.0_x64__2p2nqsd0c76g0</Data>
<Data Name="PackageRelativeAppId">App</Data>
<Data Name="HangType">Unknown</Data>
</EventData>
</Event>

Confirming that the severe input lag remains reproducible on the current Microsoft Store package OpenAI.Codex_26.727.6591.0_x64 (ChatGPT.exe/Chromium 150.0.7871.182). The Store shows no update available.

Symptoms:

• Composer input is visibly delayed and nearly unusable.
• Memory is about 2 GB during startup, settling around 1.0–1.2 GB.
• Other applications remain responsive.

Sanitized local diagnostic evidence:

• Windows recorded Event ID 1002, Application Hang, with hang type Top level window is idle.
• The same system previously recorded a hang on a 26.715 build and the 0xc06d007f crash loop on a 26.707 build. The UI problem therefore persists across later packages.
• Steady state was eight ChatGPT processes totaling about 1.1–1.2 GB resident memory: main process ~321 MB, renderers ~571 MB combined, and GPU process ~119 MB.
• Approximately 20 GB of physical memory remained available; disk activity was ~0.3%, ChatGPT GPU activity stayed below 1%, and no display-driver resets were recorded.
• In 3.8 minutes, the desktop log emitted 111 repeated GitHub operation failed: no git remotes found warnings (~29/min), plus Git snapshot became stale. One skills/list request took 4.175 seconds.
• The hidden avatarOverlay renderer appeared in 85 log entries, always invisible and unfocused, while still receiving duplicated renderer events.

This suggests the no-remote GitHub retry loop and/or hidden overlay renderer may be adding main-process/renderer contention. Could the team check whether these repeated background operations can block composer input in 26.727?

No raw logs, project names, paths, files, task content, usernames, screenshots, or attachments are included.