Windows Desktop regression: Codex uses 6+ GB RAM, ~235 MB/s disk and causes system-wide mouse lag after update

What happened?

After updating the Codex / ChatGPT Desktop app on Windows, performance regressed severely. The app now causes system-wide lag, including visible mouse stutter, even though this did not happen before the update.

Observed resource usage

During the affected state in Windows Task Manager:

• ChatGPT / Codex memory usage increased from roughly 4.5 GB to 6.4 GB
• CPU usage reached roughly 27–28%
• Disk activity reached roughly 234.9 MB/s
• Total system memory usage reached about 84% on a 16 GB RAM machine
• The whole desktop became sluggish enough that even taking screenshots was difficult
• Mouse movement visibly stuttered while Codex was active

Two WMI Provider Host processes were visible at 0% CPU during one of the captures, so this does not appear to be explained solely by the known WMI-high-CPU variant.

Regression

This behavior started after a recent Codex Desktop update. Before the update, the same machine and project did not show this level of lag.

Expected behavior

Codex Desktop should remain responsive without consuming several gigabytes of memory, generating sustained very high disk activity, or making the entire Windows desktop and mouse input stutter.

Environment

• Windows 11 x64
• 16 GB RAM
• Codex / ChatGPT Desktop app
• Local project workspace open

Additional notes

This may be related to other Windows Desktop performance regressions involving high memory usage, Git/repository refresh loops, renderer/app-server pressure, or process churn. The especially high disk throughput and rapidly increasing memory usage suggest a possible repeated scan/index/log/write loop or memory leak.

Screenshots from Task Manager showed the measurements above.

Reproduce the regression on Windows 11 x64 with a local project workspace open, then monitor ChatGPT/Codex Desktop in Windows Task Manager. Compare memory, CPU, disk activity, and mouse responsiveness with the reported post-update behavior; done means the triggering activity is identified and the resource usage or desktop lag is verified as resolved.