Menu
This is a follow-up question to my previous question.
As suggested in this answer to my previous question, I used ProcessExplorer to analyze a list of handles that my application is using to find a handle leak.
The handles that are leaking are of type Section.
What exactly is a section handle, where is it used and what can cause section handles to leak?
I'm not using memory mapped files in my code.
904
One cause of a handle leak is when a programmer mistakenly believes that retrieving a handle to an entity is simply obtaining an unmanaged reference, without understanding that a count, a copy, or other operation is actually being performed.
To troubleshoot an out-of-memory condition, use the Debug Diagnostics tool to monitor memory allocations over time. The Debug Diagnostics tool can create and analyze a memory leak dump file (. dmp). When you troubleshoot memory leaks, the goal is to attach Leaktrack.
A handle leak is a program bug that occurs when a computer program, such as Outlook, requests a connection to a resource on the computer, but does not release the connection when it has completed its task. These are not infections and cannot be fixed by Webroot.
Quoting Mark Russinovich's Inside Windows 2000 (what is now called Windows Internals),
The section object, which the Win32 subsystem calls a file mapping object, represents a block of memory that two or more processes can share.
So, it's a memory mapped file. They'd leak if you created a memory mapped file and failed to close it. Pretty hard to be much more specific.
87
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
