You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Windows Desktop 26.707.12708.0] Severe lag while typing and switching tasks; repeated 0xc06d007f crashes #33561
Microsoft Store package: OpenAI.Codex_26.707.12708.0_x64__2p2nqsd0c76g0
What platform is your computer?
Windows 11 Pro, build 26200, x64, 16 GB RAM.
What issue are you seeing?
I am seeing severe, persistent UI lag in the Windows desktop app during normal use.
The most noticeable symptoms are:
typing into the composer has a visible delay;
switching between tasks/conversations can freeze the window for several seconds;
sending a message can feel delayed before the UI accepts it;
the whole desktop sometimes feels briefly stuck while the app remains open.
This is not just a slow network connection. CPU, disk queue, and available memory were normal while the problem was happening. Windows Event Viewer repeatedly records new Application Error events for ChatGPT.exe:
I also see repeated renderer-side ResizeObserver loop completed with undelivered notifications errors in the desktop logs.
I tried the Windows Repair action and then Reset for the Codex app. The reset started a fresh app process, but the same 0xc06d007f events and severe lag returned within minutes.
What steps can reproduce the bug?
Launch Codex Desktop on Windows.
Open an existing task, then switch between tasks/conversations.
Type or submit messages normally.
Observe delayed input and intermittent UI freezes.
Check Windows Event Viewer > Windows Logs > Application and observe repeated ChatGPT.exe Event ID 1000 entries with 0xc06d007f.
The problem occurs during ordinary text-based work; no in-app browser or external device is required.
What is the expected behavior?
Typing, switching tasks, and submitting messages should stay responsive. A normal task should not generate repeated background crashes or make the rest of the desktop stutter.
Additional information
I found related reports such as #33518, #33494, and #33524 after collecting the local evidence. I am filing this separately because the same failure is still present on the newer Microsoft Store build 26.707.12708.0, even after both Repair and Reset. I have not attached raw logs because they may include private task content, but I can provide redacted event details if useful.
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 39ResizeObserver 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 zerogit 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-hidHID.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.
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.
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.
Activity
github-actions commentedon Jul 16, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
chenxupeng1990-eng commentedon Jul 16, 2026
Confirmed on the exact same Microsoft Store package:
OpenAI.Codex_26.707.12708.0_x64__2p2nqsd0c76g0.Fresh-process evidence from a controlled restart:
ChatGPT.exeprocess started at 17:53:36 local time0xc06d007fChatGPT.exeEvent ID 1000 records, all with0xc06d007fResizeObserver loop completed with undelivered notificationsentries for the fresh process, and 1,045 for the dayThe task-switch pass also showed 29 Git repo-watcher starts and 20 local Git state probes, but zero
git pullorgit fetchcommands. One local Git operation was delayed for 5.6 seconds while desktop background requests were also slow (plugin/listup to 10.5 seconds andmcpServerStatus/list22.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
0xc06d007fevents 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.
wuyongjie1990-coder commentedon Jul 16, 2026
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 identicalChatGPT.exeApplication Error event ID 1000 records with exception code0xc06d007f: 182 under the previous26.707.9981.0package and 269 under26.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-serviceloads@worklouder/device-kit-oai, whosenode-hidHID.nodedelay-imports 61 Node/N-API procedures throughnode.exe, includingnapi_create_function.ChatGPT.exeexports none of those N-API procedures, while the bundledchrome.dllexports all of them. The renderer’s Codex Micro bridge callsgetState()andupdateLighting()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
DelayLoadInfostructure, 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.subpandu commentedon Jul 17, 2026
Unusable in windows, crashing every 2 mins
subpandu commentedon Jul 17, 2026
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:
1002
0
2
101
0
0x8000000000000000
192731
Application
Datta-Home
ChatGPT.exe
150.0.7871.124
0x2030
0x1dd15ac6be7e34d
4294967295
C:\Program Files\WindowsApps\OpenAI.Codex_26.715.2305.0_x64__2p2nqsd0c76g0\app\ChatGPT.exe
ce8c3d3a-0d66-4e85-9d18-896ed4634696
OpenAI.Codex_26.715.2305.0_x64__2p2nqsd0c76g0
App
Unknown
sterling-GH commentedon Aug 3, 2026
Confirming that the severe input lag remains reproducible on the current Microsoft Store package
OpenAI.Codex_26.727.6591.0_x64(ChatGPT.exe/Chromium150.0.7871.182). The Store shows no update available.Symptoms:
Sanitized local diagnostic evidence:
Application Hang, with hang typeTop level window is idle.0xc06d007fcrash loop on a 26.707 build. The UI problem therefore persists across later packages.GitHub operation failed: no git remotes foundwarnings (~29/min), plusGit snapshot became stale. Oneskills/listrequest took 4.175 seconds.avatarOverlayrenderer 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.