In this case I noticed that the process IDs on her system had seven digits.
I believe on Windows 9x, process IDs are actual kernel addresses (pointers to the process structure), and thus always have 10 digits.
Finding a VS Code Memory Leak
11–20 of 20 posts
Re: Finding a VS Code Memory Leak
#12Earlier quoted context omitted.
There are job objects which are similar to Linux cgroups, including the ability to set a limit on the number of processes. But I'm not sure if that limit will be tripped in this case or not because the child processes have exited, whereas the job object parameter is specifically called LIMIT_ ACTIVE _PROCESS https://learn.microsoft.com/en-us/windows/win32/procthread/j... https://learn.microsoft.com/en-us/windows/win3…
OpenProcess retrieves a handle to an existing process rather than creating a process so it won't be governed by JOB_OBJECT_LIMIT_ACTIVE_PROCESS, the bug here is that it's leaking handles, not processes.
Ah yes, in that case the relevant limit would be one on total handles, which doesn't seem to exist.
Re: Finding a VS Code Memory Leak
#13> Sometimes I think it would be nice to have limits on resources in order to more automatically find mistakes like this I was actually fairly disappointed when Visual Studio (not code) went to 64-bit. Because I knew its memory usage was now going to be unconstrained. Still way better than the unapologetic gluttony of Rider but experiences showed it to be a bit leaky over time (tip: Ctrl-Alt-Shift-F12 twice does a ful…
> I was actually fairly disappointed when Visual Studio (not code) went to 64-bit.
Keep stuff on 32bit to ensure memory leaks and feature bloat are caught early, genius.
Seriously though, that might be a quick and dirty way to get an application with a hard-limit on memory for testing.
Re: Finding a VS Code Memory Leak
#14The code base for VSCode seems to be huge. With plug-ins, bloat, all the different things that it does, and large number of installations, it seems an ideal target for vulnerabilities and supply chain attacks.
Anyone knows more the level of risk?
Re: Finding a VS Code Memory Leak
#15Great analysis, but the solution is so simple: RAII.
And this is offered as `unique_process_handle`[1] in the Windows Implementation Library (WIL)[2].
This is a fantastic addition to the Windows developer's toolkit, which everyone should be using from the outset. The Windows C API is unnecessarily verbose (although this can be said of any OS, Windows' is particularly bad), and simple mistakes can and will happen.
Let RAII help you, let the mighty close-scope token `} ` be your best friend.
[1]: https://github.com/microsoft/wil/blob/1f20cd086e07b9be54e70d...
Re: Finding a VS Code Memory Leak
#16> Sometimes I think it would be nice to have limits on resources in order to more automatically find mistakes like this I was actually fairly disappointed when Visual Studio (not code) went to 64-bit. Because I knew its memory usage was now going to be unconstrained. Still way better than the unapologetic gluttony of Rider but experiences showed it to be a bit leaky over time (tip: Ctrl-Alt-Shift-F12 twice does a ful…
Even if it stayed 32 bit that wouldn't have helped with memory resources, because experience has proven that if we care about host stability extensions should be running on their own processes with OS IPC.
Which is something that VSCode does, and VS has been increasingly adopting, and I bet VS 2026 will most likely double down on it.
Which in the end means lots of processes going around to support IDE related tasks.
Re: Finding a VS Code Memory Leak
#17> Sometimes I think it would be nice to have limits on resources in order to more automatically find mistakes like this I was actually fairly disappointed when Visual Studio (not code) went to 64-bit. Because I knew its memory usage was now going to be unconstrained. Still way better than the unapologetic gluttony of Rider but experiences showed it to be a bit leaky over time (tip: Ctrl-Alt-Shift-F12 twice does a ful…
Even if it stayed 32 bit that wouldn't have helped with memory resources, because experience has proven that if we care about host stability extensions should be running on their own processes with OS IPC. Which is something that VSCode does, and VS has been increasingly adopting, and I bet VS 2026 will most likely double down on it. Which in the end means lots of processes going around to support IDE related tasks.
Right, isn't that all the more reason not to make the IDE itself 64-bit?
Re: Finding a VS Code Memory Leak
#18Earlier quoted context omitted.
Even if it stayed 32 bit that wouldn't have helped with memory resources, because experience has proven that if we care about host stability extensions should be running on their own processes with OS IPC. Which is something that VSCode does, and VS has been increasingly adopting, and I bet VS 2026 will most likely double down on it. Which in the end means lots of processes going around to support IDE related tasks.
Right, isn't that all the more reason not to make the IDE itself 64-bit?
Maybe, although there are other issues keeping 32 bit processes around on a 64 bit OS.
Re: Finding a VS Code Memory Leak
#19In 2021 I found an invisible memory leak in a tool (VS Code) that I have never used. This is the story of how.
If you look at the commits for the process.cc file, you can see that the ORIGINAL version of the GetProcessMemoryUsage function was correct.
for original function, see process.cc, lines 36-53 in https://github.com/microsoft/vscode-windows-process-tree/com...
A week later, when the GetCpuUsage function was added to process.cc, the CloseHandle call at the end of GetProcessMemoryUsage was deleted/pushed into GetCpuUsage.
for updated code, see process.cc, lines 53-96, in https://github.com/microsoft/vscode-windows-process-tree/com...
The unified diff for that change doesn't point out that code was deleted from GetProcessMemoryUsage (the CloseHandle() call is now in GetCpuUsage).
Someone ok'd those changes...
Also MS's PREfast/PREfix static code analysis tools missed that bug as well. I'd update my static analysis perl script to check for that case, but one of the comments to TFA said chatgpt will catch the problem, so I'll punt.
Minor nit: The ProcessInfo struct declares fields in an awkward fashion if you're debugging, esp. if you're viewing memory of the struct. One should put small size fields at the start of the struct, large size fields at the end. As is, the large name character array will occupy a large amount of space and if you want to see the values of the small fields, one would probably have to scroll to locate these small fields after the large character array.
Minor nit: What's with the magic number 1024? At least in recent versions of the process.cc file, they've gone from a fixed 1024 element array (each element == MAX_PATH * TCHAR + sizeof(DWORD)*3 bytes) to a dynamic array.