windows vscode opencode extension process freeze #6942

Closed
opened 2026-02-16 18:05:40 -05:00 by yindo · 5 comments
Owner

Originally created by @caozhiyuan on GitHub (Jan 20, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

windows vscode opencode extension process freeze: when switching vscode to the background (for example, opening a browser and working for a while), after some time returning to vscode, the opencode extension window becomes unresponsive. The vscode subprocess consistently uses 25% CPU.

Plugins

No response

OpenCode version

1.1.27

Steps to reproduce

  1. let opencode run some task in vscode extension opencode
  2. opening a browser and working for a while
  3. back to vscode

Screenshot and/or share link

No response

Operating System

windows 11

Terminal

pwsh

Originally created by @caozhiyuan on GitHub (Jan 20, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description windows vscode opencode extension process freeze: when switching vscode to the background (for example, opening a browser and working for a while), after some time returning to vscode, the opencode extension window becomes unresponsive. The vscode subprocess consistently uses 25% CPU. ### Plugins _No response_ ### OpenCode version 1.1.27 ### Steps to reproduce 1. let opencode run some task in vscode extension opencode 2. opening a browser and working for a while 3. back to vscode ### Screenshot and/or share link _No response_ ### Operating System windows 11 ### Terminal pwsh
yindo added the windowsbugperf labels 2026-02-16 18:05:40 -05:00
yindo closed this issue 2026-02-16 18:05:41 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 20, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #9599: opencode crashes over and over (also Windows-specific with high CPU usage and 25%+ CPU consumption)
  • #8667: High CPU usage just by waiting user input (Windows/VSCode environment, CPU spike during idle)
  • #8484: Screen lag/freezing when typing text (Windows 11, freezing behavior)
  • #7893: Severe scroll lag in VSCode integrated terminal on WSL2 (VSCode unresponsiveness on Windows 11)
  • #6172: High CPU usage during LLM streaming (root cause analysis showing O(n) text buffer rendering causing sustained CPU)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 20, 2026): This issue might be a duplicate of existing issues. Please check: - #9599: opencode crashes over and over (also Windows-specific with high CPU usage and 25%+ CPU consumption) - #8667: High CPU usage just by waiting user input (Windows/VSCode environment, CPU spike during idle) - #8484: Screen lag/freezing when typing text (Windows 11, freezing behavior) - #7893: Severe scroll lag in VSCode integrated terminal on WSL2 (VSCode unresponsiveness on Windows 11) - #6172: High CPU usage during LLM streaming (root cause analysis showing O(n) text buffer rendering causing sustained CPU) Feel free to ignore if none of these address your specific case.
Author
Owner

@caozhiyuan commented on GitHub (Jan 20, 2026):

@rekram1-node There is no issue when opening outside the VSCode internal terminal; however, when opening within VSCode and using it for a while, it causes the VSCode subprocess CPU usage to spike to about 25%, after which the OpenCode interface freezes.

@caozhiyuan commented on GitHub (Jan 20, 2026): @rekram1-node There is no issue when opening outside the VSCode internal terminal; however, when opening within VSCode and using it for a while, it causes the VSCode subprocess CPU usage to spike to about 25%, after which the OpenCode interface freezes.
Author
Owner

@caozhiyuan commented on GitHub (Jan 20, 2026):

Problem process:
CommandLine="C:\Users\xxx\AppData\Local\Programs\Microsoft VS Code\Code.exe" --type=renderer --user-data-dir="C:\Users\xxx\AppData\Roaming\Code" --standard-schemes=vscode-webview,vscode-file --enable-sandbox --secure-schemes=vscode-webview,vscode-file --cors-schemes=vscode-webview,vscode-file --fetch-schemes=vscode-webview,vscode-file --service-worker-schemes=vscode-webview --code-cache-schemes=vscode-webview,vscode-file --app-user-model-id=Microsoft.VisualStudioCode --app-path="C:\Users\xxx\AppData\Local\Programs\Microsoft VS Code\resources\app" --enable-sandbox --enable-blink-features=HighlightAPI --max-active-webgl-contexts=32 --disable-blink-features=FontMatchingCTMigration,StandardizedBrowserZoom, --video-capture-use-gpu-memory-buffer --lang=en-US --device-scale-factor=2.5 --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=4 --time-ticks-at-unix-epoch=-1767168900234389 --launch-time-ticks=1796835869402 --field-trial-handle=1836,i,1728646702783304408,6593918439366806803,262144 --enable-features=DocumentPolicyIncludeJSCallStacksInCrashReports,EarlyEstablishGpuChannel,EnableTransparentHwndEnlargement,EstablishGpuChannelAsync --disable-features=CalculateNativeWinOcclusion,LocalNetworkAccessChecks,ScreenAIOCREnabled,SpareRendererForSitePerProcess,TraceSiteInstanceGetProcessCreation --variations-seed-version --trace-process-track-uuid=3190708990060038890 --mojo-platform-channel-handle=3284 --vscode-window-config=vscode:32c12368-c66b-4e8a-8e2c-02b8a5d68d02 /prefetch:1

@caozhiyuan commented on GitHub (Jan 20, 2026): Problem process: CommandLine="C:\Users\xxx\AppData\Local\Programs\Microsoft VS Code\Code.exe" --type=renderer --user-data-dir="C:\Users\xxx\AppData\Roaming\Code" --standard-schemes=vscode-webview,vscode-file --enable-sandbox --secure-schemes=vscode-webview,vscode-file --cors-schemes=vscode-webview,vscode-file --fetch-schemes=vscode-webview,vscode-file --service-worker-schemes=vscode-webview --code-cache-schemes=vscode-webview,vscode-file --app-user-model-id=Microsoft.VisualStudioCode --app-path="C:\Users\xxx\AppData\Local\Programs\Microsoft VS Code\resources\app" --enable-sandbox --enable-blink-features=HighlightAPI --max-active-webgl-contexts=32 --disable-blink-features=FontMatchingCTMigration,StandardizedBrowserZoom, --video-capture-use-gpu-memory-buffer --lang=en-US --device-scale-factor=2.5 --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=4 --time-ticks-at-unix-epoch=-1767168900234389 --launch-time-ticks=1796835869402 --field-trial-handle=1836,i,1728646702783304408,6593918439366806803,262144 --enable-features=DocumentPolicyIncludeJSCallStacksInCrashReports,EarlyEstablishGpuChannel,EnableTransparentHwndEnlargement,EstablishGpuChannelAsync --disable-features=CalculateNativeWinOcclusion,LocalNetworkAccessChecks,ScreenAIOCREnabled,SpareRendererForSitePerProcess,TraceSiteInstanceGetProcessCreation --variations-seed-version --trace-process-track-uuid=3190708990060038890 --mojo-platform-channel-handle=3284 --vscode-window-config=vscode:32c12368-c66b-4e8a-8e2c-02b8a5d68d02 /prefetch:1
Author
Owner

@caozhiyuan commented on GitHub (Jan 21, 2026):

after disable animations , The process will not hang now @rekram1-node

@caozhiyuan commented on GitHub (Jan 21, 2026): after disable animations , The process will not hang now @rekram1-node
Author
Owner

@caozhiyuan commented on GitHub (Jan 21, 2026):

also set OPENCODE_DISABLE_TERMINAL_TITLE=1

@caozhiyuan commented on GitHub (Jan 21, 2026): also set OPENCODE_DISABLE_TERMINAL_TITLE=1
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6942