Finding a VS Code Memory Leak

A developer discovered a 64 GB memory leak in VS Code by noticing seven-digit process IDs during a pair-programming session, indicating a process handle leak. The investigation revealed that OpenProcess calls lacked corresponding CloseProcess calls, causing roughly 64 KiB of memory to leak per unclosed handle. Using Windows handle leak debugging techniques and tools, the root cause was identified within an hour—a single missing line of code in the process memory usage function. The bug was reported and fixed within days.