在登录但处于空闲状态时,GitHub Copilot Chat 会将共享扩展主机阻塞整整 5 秒(单个同步 `consume` 调用),从而破坏其他扩展的 Web 视图。

exthost-ba2e1f.cpuprofile exthost-c351c5.cpuprofile renderer-unresponsive-excerpt.log exthost-33fc07.cpuprofile exthost-450caa.cpuprofile - Copilot Chat Extension Version: 0.66.0 (bundled with VS Code 1.138.0, publisher: GitHub, buildType: prod) - VS Code Version: 1.138.0 (system installer, C:\Program Files\Microsoft VS Code) - OS Version: Windows 11 Pro 25H2, build 26200.9457 (64-bit), 13th Gen Intel i7-13700HX (16C/24T), 31.6 GB RAM, NVMe SSD - Feature (e.g. agent/edit/ask mode): Not using Copilot at all — no request in flight, chat view not open. Copilot Chat was signed in and running in the background only (Got Copilot token for <user>; sku free_limited_copilot). The stalls occur in background/startup processing of the shared extension host. - Selected model (e.g. GPT 4.1, Claude 3.7 Sonnet): Not applicable — I never sent a request. Copilot Chat's own log shows BYOK: registered 9 provider(s) and no model was selected by me. - Logs: See "Logs and profiles" below. Key line, repeated 4 times across 4 separate window launches: UNRESPONSIVE extension host: 'GitHub.Copilot-chat' took 99.88961883031027% of 5013.432ms, saved PROFILE here: 'file:///c%3A/Users/.../exthost-c351c5.cpuprofile' Renderer log: %APPDATA%\Code\logs\<session>\window1\renderer.log Copilot Chat log: %APPDATA%\Code\logs\<session>\window1\exthost\GitHub.Copilot-chat\GitHub Copilot Chat.log Steps to Reproduce: 1. Open VS Code 1.138.0 with Copilot Chat 0.66.0 enabled (default bundled state), signed in, in a workspace with large file trees — in my case two roots, one of them a WSL remote folder, plus a sibling tool's session store under the user profile holding ~11,000 files / 3.3 GB that is walked on a timer. 2. Use the editor normally and do NOT interact with Copilot — do not open Chat, do not send any request. 3. Wait. Within 1–3 minutes the extension host is reported unresponsive. VS Code's own profiler attributes the entire 5 s window to Copilot Chat. 4. Observed 4 times in 4 separate window launches over ~25 minutes (15:11, 15:18, 15:21, 15:35 local). Recorded twice again in a 2-minute-old session right after a reboot, so it is not session state. Actual behavior: Copilot Chat holds the shared extension host for a full 5000 ms in a single synchronous call and never yields to the event loop for that entire window. VS Code's unresponsive check only fires at ~5 s, so 5000 ms is the observed floor, not necessarily a ceiling. During the stall every other extension in the same host is frozen: input into webview panels lags (the extension's own webviews report …