High CPU Usage in VS Code "window" process after installing Codex extension

Resolved 💬 2 comments Opened Apr 15, 2026 by DanielTseng2004 Closed Apr 15, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the IDE extension are you using?

26.409.20454

What subscription do you have?

free

Which IDE are you using?

vs code

What platform is your computer?

windows 11 25H2

What issue are you seeing?

<img width="1032" height="561" alt="Image" src="https://github.com/user-attachments/assets/4f8e6a6a-8b8e-43ab-9fba-4e12be5d45a2" />

Observed High CPU Usage in VS Code "window" process

After installing and enabling the extension, the VS Code "window" (main renderer) process exhibits high CPU usage (10%–15% even when idle). This leads to noticeable UI lag and editor latency during development.

Key Evidence:

  • The issue disappears immediately when the extension is disabled.
  • The "window" process is the primary consumer in VS Code Process Explorer.

What steps can reproduce the bug?

  1. Install the extension in VS Code.
  2. Open a project (e.g., a Vue/Vite project or any folder with several source files).
  3. Ensure ChatGPT: Comment Code Lens Enabled is toggled ON in the extension settings.
  4. Open the VS Code Process Explorer (Help > Open Process Explorer).
  5. Observe the CPU usage of the "window" process.
  6. Toggle the CodeLens setting or the extension itself to see the CPU usage drop/spike.

Example Code Snippet (Triggering CodeLens):
// Any file containing TODO comments, for example:
// TODO: Implement a new feature here.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

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

  • #17429
  • #17856
  • #17394

Powered by Codex Action

DanielTseng2004 · 4 months ago

Reply to GitHub Issue:

Thank you for the quick feedback and the information provided by the bot.

I can confirm that downgrading the extension to version 0.4.79 resolved the high CPU usage in the VS Code "window" process. After the downgrade, the CPU usage returned to normal levels (under 1% when idle).

It appears that the recent versions might have a regression in how the UI or the chat list is rendered, as mentioned in #17429. I will stick with this version for now until a fix is released.

I am closing this issue as a duplicate of #17429. Thanks again!