Skip to content

Comment on Finding a VS Code Memory Leakparent

Comments

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.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.