After the update to Windows 11, the mouse has become noticeably sluggish.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
版本 26.810.41047
What subscription do you have?
plus
What platform is your computer?
x86 win11
What issue are you seeing?
After the update to Windows 11, the mouse has become noticeably sluggish. Below are the troubleshooting results conducted by Codex
Investigation conclusion: The issue is not with the mouse malfunctioning, but primarily due to the sustained high load experienced by Codex after today's update.
I confirm that:
Codex was updated at 13:49 today, and the current version is 26.810.4967.0.
Even without any operations, one of the background tasks still occupies a multiprocessor core for an extended period.
The total memory usage of all Codex components is approximately 2.6GB, with significant fluctuations ranging from 500MB to 900MB.
The log shows that it repeatedly initiates project directory monitoring, with a total of 28 launches, accompanied by multiple status check exceptions. It is highly likely that the monitoring task did not end normally, leading to an increasing operational burden as it continues to run.
The graphics card usage is only about 4% to 6%, and there are no records of graphics card, mouse, or application crashes, so full graphics card usage and mouse malfunction are not the main causes.
There is a "remote viewing" virtual screen driver on the machine, which may amplify the sense of stuttering, but it is not the source of this issue.
After closing Codex, everything returned to normal, which is fully consistent with the aforementioned inspection results.
Therefore, we can confidently conclude that this is a performance issue with today's Codex version, where the project directory monitoring or interface backend task has entered a repetitive loop. Currently, there is no public statement regarding this version in the official documentation, so we cannot be 100% certain about the specific internal function that has gone wrong. However, the source of the problem has been pinpointed to Codex itself.
What steps can reproduce the bug?
Feedback ID: 019fffda-afd0-7f30-92db-175e807f6243
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Feedback ID 019fffda-afd0-7f30-92db-175e807f6243 and the report's project-directory monitoring and status-check exceptions after the Windows 11 update. Reproduce the idle Codex workload while watching CPU, memory, and monitoring activity. Done means the background loop no longer causes sustained high load, excessive memory use, or sluggish mouse response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100