microsoft / microsoft/vscode-remote-release

Memory leak from repeatedly spawing process

Open
#11,268 3 comments 0 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Oct 22, 2025.

bug containers upstream
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Type: Bug

Open vscode, watch task manager for docker.exe to start and close rapidly. After letting vscode run for a few hours this docker.exe will have started and closed hundreds of times, eating up ram every time. Run Rammap and look at the processes tab. You will see a long list of old docker.exe and conhost.exe processes holding on to memory. The only way to clear it is to reboot the computer. It will cause games to slow down and the computer to freeze after a few day. I am committed to resolving this issue so let me know if you need more information or even remote access to my computer to inspect it.

Extension version: 0.427.0
VS Code version: Code 1.105.1 (7d842fb85a0275a4a8e4d7e040d2625abbf7f084, 2025-10-14T22:33:36.618Z)
OS version: Windows_NT x64 10.0.26100
Modes:

System Info
Item Value
CPUs AMD Ryzen 9 7950X 16-Core Processor (32 x 4491)
GPU Status 2d_canvas: enabled
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 63.16GB (46.08GB free)
Process Argv --crash-reporter-id 8b69bfc5-b790-44cc-b5ea-0bc7ca66fbfa
Screen Reader no
VM 0%
A/B Experiments
vsliv368:30146709
pythonvspyt551:31249599
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
aj953862:31281341
4f60g487:31327383
nes-set-on:31351930
63221493:31336333
envsactivate1:31353494
gendocstringt:31405074
gaj49834:31404438
cloudbuttont:31379625
todos-1:31405332
qwen_all_req:31402696
treatment_gpt5applypatchexclusively:31398171
3efgi100_wstrepl:31403338
trigger-command-fix:31379601
auto_model_enabled:31385282
use-responses-api:31390855
applesignin:31399435
auto_g2946222:31405799
ddidtcf:31399634
nes-subseq-delay-200:31400950
6j29d282:31402215
afag3459:31405348

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.