[Windows] Severe input lag and UI freezes when opening app and typing in chat #34450

Activity

1. lints123

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Jul 21, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   performance

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   on Jul 21, 2026
3. github-actions commented on Jul 21, 2026

   

   github-actionsbot

   on Jul 21, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Codex App is extremely laggy and frequently freezes during use #33604
   • [Windows Desktop 26.707.12708.0] Severe lag while typing and switching tasks; repeated 0xc06d007f crashes #33561
   • [Windows Desktop 26.715] Completed large thread is fully replayed every few seconds, causing system-wide input stutter #33786

   Powered by Codex Action
4. weijunswj commented on Jul 23, 2026

   

   weijunswj

   on Jul 23, 2026

   More actions

   Additional Windows reproduction with measured resource data:

   • Codex/ChatGPT desktop: 26.715.10079.0
   • Windows 11 Home 25H2, build 26200.8894, x64
   • Symptom: approximately 1–3 seconds of input latency per character while an existing task is active. Restarting the app and Windows did not resolve it.
   • The active local transcript was only 0.53 MB; the largest transcript on the machine was 1.48 MB, so long conversation history was not required.
   • Codex-related processes used about 1.3 GB working set in total and approximately 0.1% CPU during the sample.
   • The system had 15.7 GB RAM with only 1.6–1.9 GB available. An 8-second sample averaged roughly 31,649 Pages/sec and 543 Page Reads/sec, indicating severe paging.
   • Microsoft-signed SrTasks.exe (System Protection background tasks) grew from about 3.3 GB to 5.7 GB private memory during the investigation and averaged about 4,850 page faults/sec.
   • Windows Event Log timing was unusually tight: SrTasks.exe started at 22:42:35 under the Windows Update service, the Codex Store update began at 22:42:36, and the update completed at 22:42:58.
   • Codex logs contained no OOM, renderer-crash, or GPU-crash indicators.

   This does not prove that SrTasks.exe is the app-side root cause, but it shows a reproducible memory-pressure/update interaction capable of making the Chromium UI nearly unusable. A useful control would be to retest input latency after the System Protection process exits and available RAM recovers.
5. SilverSeraphim commented on Jul 27, 2026

   

   SilverSeraphim

   on Jul 27, 2026

   More actions

   I have this problem too
6. linhuan123 commented on Aug 8, 2026

   

   linhuan123

   on Aug 8, 2026

   More actions

   [Windows] Codex desktop: main process burns ~50% of one core constantly, causing severe typing lag (26.803.5235.0)

   Environment: OpenAI.Codex 26.803.5235.0 (Microsoft Store), Windows 11 10.0.26200 x64

   Symptoms:

   • Typing in the chat input has noticeable delay/jank; the rest of the UI responds.
   • The ChatGPT.exe browser process uses ~50% of one core continuously:
     • 172s CPU in 5.2 min in a fresh session (~55% avg)
     • persists across restarts, when minimized, and while idle in a brand-new task
     • renderers, GPU process, and app-server all idle (<1%); disk writes 0 KB

   Per-thread sampling (main process):

   • one hot thread starting in ChatGPT.exe (~32% of a core)
   • three hot threads in chrome.dll (~8% each)

   Logs (5 min): ~900 rejected requests (~3/s):

   • "invalid thread id / invalid session id: ... found u at 2" with conversationId="current"
   • methods thread/read + thread/resume, source=thread_hydration

   Not related to #33409: no 0xC06D007F; serialport ABI already fixed (bindings.node exports napi_register_module_v1).

   Already ruled out: restart, minimize, closing avatar-overlay/pet windows, new task, HID devices, IME processes, GPU, disk writes.

   Likely a busy loop in the Electron main process tied to thread-hydration retries using the literal id "current".