[New post] Finding Windows HANDLE leaks, in Chromium and others

brucedawson posted: "Three years ago I found a 32 GB memory leak caused by CcmExec.exe failing to close process handles. That bug is fixed, but ever since then I have had the handles column in  Windows Task Manager enabled, just in case I hit another handle leak. Because" Respond to this post by replying above this line New post on Random ASCII - tech blog of Bruce Dawson Finding Windows HANDLE leaks, in Chromium and others by brucedawson Three years ago I found a 32 GB memory leak caused by CcmExec.exe failing to close process handles. That bug is fixed, but ever since then I have had the handles column in  Windows Task Manager enabled, just in case I hit another handle leak. Because of this routine checking I noticed, in February of 2021, that one of Chrome's processes had more than 20,000 handles open! This Chrome bug is fixed now but I wanted to share how to investigate handle leaks because there are other leaky programs out there. I also wanted to share my process of learning. Continue reading "Finding Windows HANDLE leaks, in Chromium and others" brucedawson | July 25, 2021 at 11:21 pm | Tags: handles, leaks | Categories: Bugs, Code Reliability, Investigative Reporting, uiforetw, xperf | URL: https://wp.me/p1fTCO-Yp Comment    See all comments    Like Unsubscribe to no longer receive posts from Random ASCII - tech blog of Bruce Dawson. Change your email settings at Manage Subscriptions. Trouble clicking? Copy and paste this URL into your browser: https://randomascii.wordpress.com/2021/07/25/finding-windows-handle-leaks-in-chromium-and-others/ Thanks for flying with WordPress.com