Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix High CPU in second VS Code project window when Codex panel is opened, while first project window is already open [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19091•Fetched 2026-04-24 06:01:09
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
1
Author
MinePacuMinePacu
Participants
github-actions[bot]github-actions[bot]hommhommMinePacuMinePacu
Timeline (top)
commented ×2labeled ×2cross-referenced ×1mentioned ×1
RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

26.5417.40842 (latest prerelease)

What subscription do you have?

Plus

Which IDE are you using?

VS Code

What platform is your computer?

macOS on Mac mini (M4) (Darwin 25.4.0 arm64 arm)

What issue are you seeing?

When I open Codex in a second VS Code window that already has a workspace/project open, CPU usage spikes sharply in Code Helper (Renderer).

The first VS Code window also already has a project/workspace open, but it does not show the same high CPU behavior by itself. The spike happens when Codex is opened in the second project window.

This does not require any active chat. The issue happens even when the Codex panel is simply opened and left idle.

From VS Code's Help → Open Process Explorer, the highest consumer is the second project window (window[index]).

Observed behavior so far:

  • First window already has a workspace/project open, and Codex can be open there with normal / low CPU
  • Opening a second empty window: normal / low CPU
  • Opening Codex in the second empty window: normal / low CPU
  • Closing Codex in the second window, then opening a project/workspace there: normal / low CPU
  • Opening Codex in that second project window: CPU becomes high
  • This also reproduces with a very small / nearly empty folder, so it does not seem tied to one large project
  • It also reproduces with no chat messages at all

What steps can reproduce the bug?

  1. Open VS Code window [# 1]
  2. Open any workspace/project folder in window [# 1]
  3. Open the Codex panel in window #1
  4. Confirm CPU usage is normal
  5. Open VS Code window [# 2]
  6. Do not open a project yet; optionally open the Codex panel and confirm CPU is still normal
  7. In window [# 2], open any workspace/project folder (this also reproduces with a very small folder)
  8. Open the Codex panel in window [# 2]

What is the expected behavior?

Opening the Codex panel in a second VS Code window with a workspace open should not cause sustained high CPU usage in Code Helper (Renderer) / window[index], especially while idle and without any chat activity.

Additional information

No response

extent analysis

TL;DR

The issue can be mitigated by closing and reopening the second VS Code window after opening a project/workspace, or by investigating the Code Helper (Renderer) process for potential resource leaks.

Guidance

  • Verify that the high CPU usage is indeed caused by the Code Helper (Renderer) process in the second VS Code window by checking the Process Explorer.
  • Try closing and reopening the second VS Code window after opening a project/workspace to see if the issue persists.
  • Investigate if there are any known issues with the Code Helper (Renderer) process in the latest prerelease version of the IDE extension (26.5417.40842).
  • Consider testing with a different project/workspace in the second window to rule out any project-specific issues.

Notes

The issue seems to be specific to the interaction between the IDE extension, VS Code, and the macOS platform, and may require further investigation to determine the root cause.

Recommendation

Apply workaround: Close and reopen the second VS Code window after opening a project/workspace, as this may help mitigate the high CPU usage issue until a more permanent fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#retrieval issue#search optimization#API routing#API middleware#SSR setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING