Anyone know a decent tool for finding memory leaks? (Even being able to reliably and automatically determine *if* there's a leak would be good...)
Last update on .
Pinning down memory leaks in large-ish systems with large numbers of libraries is a bit of a pain. I wind up using the silly Windows task manager (yes, I'm still using Windows, despite having fixed Linux (sort-of) a while ago). Sure, I don't do this very often, but would be nice to have tools when I do find myself doing it.
Comments are closed.
Pingbacks are closed.
Blake Winton on 11/30/2004 8:26 a.m. #
Process Explorer, from http://www.sysinternals.com/ seems like it will do something at least close to what you want. I've used it to track down dll issues, but I'm not sure if (or how well) it handles non-dynamic libraries.
Mike Fletcher on 11/30/2004 2:12 p.m. #
Thanks, Blake. Will give it a try.
Mike Fletcher on 11/30/2004 3:24 p.m. #
And it does, indeed, help. Particularly, it has a "high water" mark which can be used to see whether a process is actually leaking memory, or merely growing a given cache to a certain value and then stopping.<br />
Still takes a long time to fill up the caches to eliminate a given potential problem, but I've eliminated one of the test cases I *thought* was a culprit using it.<br />
Next one on the list is being a bit of a PITA (it was stable for about 10 minutes, then started growing again :( ), but oh well, at least I can see the effect now.