Looking for memory leak, I've been using MemProof and have the ability to see live counts of assets getting used, produced and destroyed. After getting run my program for more than each day and half, I've observed that anything else being constant or less, Virtual Memory (VM) is growing in counts. It began out at 109 and it is now at 113 after 24 hrs.

This is exactly what MemProof states for every VM leak:

VirtualAlloc(address_location, 16384, 4096, 4) It's recognized as Virtual Memory and it is dimensions are always 16384. API title is VirtualAlloc. The module is kernel32.dll.

In addition, memproof states, "virtualalloc reserves or commits an area of pages within the virtual address space from the calling process. Allotted pages should be freed with virtualFree when no more needed."

VM leak is connected having a function within the file System.Pas.

The function is the following:

function GetCmdShow: Integer;
var
  SI: TStartupInfo;
begin
  Result := 10;                  { SW_SHOWDEFAULT }
  GetStartupInfo(SI);
  if SI.dwFlags and 1 <> 0 then  { STARTF_USESHOWWINDOW }
    Result := SI.wShowWindow;   
end;  <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

I've the under signs pointing in the key phrase "finish" is how Memproof takes me to after i click virtual memory leak(s).

So, exactly what does this suggest?

Delphi's FastMM memory manager creates the surface of the Home windows memory system. It allocates large blocks of memory in the OS with VirtualAlloc, after which divides that up into more compact portions for the program to utilize. Should you free considerable amounts of memory, it'll give a lot of it to the OS. Should you free small quantities of memory, though, it's prone to hold onto it because you are prone to require it again soon. This really is a part of why is FastMM fast, and it is not really a memory leak.

Any memory profiler that only watches VirtualAlloc and does not really give consideration as to the FastMM does will provide you with results that do not seem sensible. As David pointed out within the comment, if you wish to find real memory leaks, you should utilize the FastMM tools. Download the entire version of FastMM from SourceForge and browse the documentation to discover how you can enable FullDebugMode and leak confirming and logging, you'll also find a significantly simpler duration of it.