Repository navigation
Description
Description
OOM error happens consistently on my main linux ssh vm workspace. Survives restarts and everything. Only workaround is for me to create a new VM. Please help
2026-11-09 17:38:13.805 [info] Extension host with pid 32424 exited with code: 0, signal: unknown.
2026-11-09 17:42:44.598 [info] Extension host with pid 2264 exited with code: 0, signal: unknown.
2026-11-09 17:42:50.177 [info] Extension host with pid 34500 exited with code: 0, signal: unknown.
2026-11-09 17:42:55.194 [info] Extension host with pid 6480 exited with code: 0, signal: unknown.
2026-11-09 17:42:57.143 [info] Extension host with pid 31560 exited with code: 0, signal: unknown.
2026-11-09 17:43:05.668 [info] Extension host with pid 35464 exited with code: 0, signal: unknown.
2026-11-09 17:46:04.702 [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
2026-11-09 17:46:04.718 [info] Extension host with pid 33092 exited with code: 0, signal: unknown.
2026-11-09 17:48:35.688 [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
2026-11-09 17:48:35.715 [info] Extension host with pid 51156 exited with code: 0, signal: unknown.
2026-11-09 17:49:23.988 [info] update#setState checking for updates
2026-11-09 17:49:24.084 [info] update#setState idle
2026-11-09 17:54:17.478 [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
2026-11-09 17:54:17.493 [info] Extension host with pid 20308 exited with code: 0, signal: unknown.
2026-11-09 17:56:26.070 [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)
2026-11-09 17:58:27.622 [error] [uncaught exception in main]: Error: Render frame was disposed before WebFrameMain could be accessed
2026-11-09 17:58:27.622 [error] Error: Render frame was disposed before WebFrameMain could be accessed
at S (file:///C:/Users/matusl/AppData/Local/Programs/Microsoft%20VS%20Code/c4453f8ea4/resources/app/out/mainImpl.js:164:8047)
at Function. (file:///C:/Users/matusl/AppData/Local/Programs/Microsoft%20VS%20Code/c4453f8ea4/resources/app/out/mainImpl.js:164:8558)
2026-11-09 18:00:51.620 [info] Extension host with pid 54088 exited with code: 0, signal: unknown.
2026-11-09 18:02:39.638 [error] [uncaught exception in main]: Error: Render frame was disposed before WebFrameMain could be accessed
2026-11-09 18:02:39.638 [error] Error: Render frame was disposed before WebFrameMain could be accessed
at S (file:///C:/Users/matusl/AppData/Local/Programs/Microsoft%20VS%20Code/c4453f8ea4/resources/app/out/mainImpl.js:164:8047)
at Function. (file:///C:/Users/matusl/AppData/Local/Programs/Microsoft%20VS%20Code/c4453f8ea4/resources/app/out/mainImpl.js:164:8558)
Issue Details
| Item | Value |
|---|---|
| Issue Category | Bug |
| Target | Visual Studio Code |
| Repository | Microsoft/vscode |
| VS Code Version | Code 1.145.2 (c4453f8, 2026-11-06T04:28:13Z) |
| OS Version | Windows_NT x64 10.0.26300 |
Activity
[Perf] search: compact file results (Written by Copilot)
aeschli commentedon Nov 13, 2026
Thanks for the report. These reports look related, although we have not confirmed that they share the same root cause:
To help identify the cause:
Heap snapshots can contain source code, paths, credentials and other private content. Please do not attach them publicly; arrange a private transfer with a maintainer. A reproduction using synthetic data is preferable.
If snapshots are not possible, a native crash dump can also help. Follow the documented procedure: quit all VS Code instances, launch locally on Windows with
code --crash-reporter-directory C:\vscode-crashes, reproduce, and arrange a private transfer of the resulting.dmpfile. Crash dumps can also contain private data; please do not upload them publicly.aeschli commentedon Nov 13, 2026
Given that disabling the Microsoft Edge Tools extension resolves the issue, this looks related to microsoft/vscode-edge-devtools#4970. That report also describes renderer memory growth and crashes in a large Remote-SSH workspace, with memory stabilizing after disabling Edge Tools.
The extension's fix, microsoft/vscode-edge-devtools#5083, was merged on November 2. It removes the startup workspace-wide file scan that could exhaust memory on large or remote workspaces. We have not yet verified which published extension version includes that fix; please check whether an update containing it is available. Disabling Edge Tools is a workaround meanwhile.
An older similar Windows/SSH report is microsoft/vscode-edge-devtools#1882.
matusthemostlygreat commentedon Nov 13, 2026
this was caused by microsoft/vscode-edge-devtools#5083
uninstalling the extension fixes the issue