Intermittent Memory Leak

[Bill Burwell]

Which memory properties, or what combinations of memory properties, provide
useful information about a program's memory usage when that program has just
started leaking memory?

While I have a VB bias, it seems to me the answer to this question should be
generic - that is language independent.

In MSDN I found the following 7 Process properties that relate to the size
of memory usage - I may have missed some. The 7 properties are shown below
with their MSDN definitions; I find the definitions to be vague and
ambiguous.

I assume that the 3 properties with names starting Peak. refer to maximum
memory values - since the program started executing. Which seems to put
them out of the running when hunting for a memory leak - except that the
Peaks would be seeing higher and higher highs as memory leaks.

The Process properties that relate to the size of memory usage -

o NonpagedSystemMemorySize - The amount of memory the system has
allocated for the associated process that cannot be written to the virtual
memory paging file.

o PagedMemorySize - The amount of memory allocated by the associated
process that can be written to the virtual memory paging file.

o PagedSystemMemorySize - The amount of memory the system has
allocated for the associated process that can be written to the virtual
memory paging file.

o PeakPagedMemorySize - The maximum amount of memory allocated by the
associated process that could be written to the virtual memory paging file.

o PeakVirtualMemorySize - The maximum amount of virtual memory that
the associated process has requested.

o PeakWorkingSet - The maximum amount of physical memory that the
associated process has required all at once.

o PrivateMemorySize - The number of bytes allocated by the associated
process that cannot be shared with other processes.