Search code examples
windowsdelphidelphi-xehandleresource-leak

What can cause section handle leaks?

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.

Solution

  • 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.