Depending on the sample interval you could grab it for _Total, and some suspect processes. If Private Bytes for Total shows an upward stepping pattern then you probably have a leak and you should lok for a corrollary shape for the same counter with one of your suspect processes.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Cooper Sent: Tuesday, March 11, 2003 8:08 AM To: NT 2000 Discussions Subject: Re: Memory leak identification ----- Original Message ----- From: "Patrick R. Sweeney" <[EMAIL PROTECTED]> Sent: Tuesday, March 11, 2003 12:07 PM > You can use Performance monitor to identify and isolate memory leaks. > http://support.microsoft.com/servicedesks/webcasts/so_projects/so2/sob > lu > rb2.asp Thanks very much for this. I am familiar with performance monitor, but this presentation states: "Under the process object, click the Handle Count, Pool Nonpaged Bytes, Pool Paged Bytes, and Private Bytes counters for the process that may be having the problem." The problem I have right now is determining whether it is actually a memory leak, and if so which process it is likely to be. Thanks again. Regards, Adrian Cooper. ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
