Much has been written about using Performance Monitor to detect and isolate memory leaks. Two KB articles on the subject are Q130926 and Q150934.
While these standard protocols work, the hit and miss method of finding the leaking process can be very time consuming. Here is an alternate method:
1. Start PMON.EXE from the Resource Kit.
2a. Monitor Paged and Non-Paged pool usage (last 2 items on the 2nd row).
If these are increasing over time, you have a memory leak.
2b. Monitior the commit counters on the 2nd row.
Increasing numbers over serval hours indicate a probable leak.
2c. Monitor the Commit Charge column.
The process with the leak will have an increasing value.
3. To make it easier to monitor, copy the output to the clipboard and paste it into notepad.
Do this about once an hour over the duration of your testing.
FortyPoundHead has posted a total of 1975 articles.
You can find more information from FortyPoundHead by visiting .
No comments on this post yet!
Do you have a thought relating to this post? You can post your comment here. If you have an unrelated question, you can use the Q&A section to ask it.
Or you can drop a note to the administrators if you're not sure where you should post.