Hunting a .NET Memory Leak
Does anyone have any reccomendations for tools or techniques to hunt down a memory leak in a .NET WinForms app?
Automated QA has a profiler that should help out: AQtime .NET Edition
How do you get a memory leak in a GC language?
It's probably not a C++ style memory leak. The objects in question are probably still referenced from SOMEWHERE. The problem is that somewhere can be fairly obscure.
Oh. That really sucks. :>(
Conclusion: .NET and other garbage collected languages still require you to track memory allocation. There's no substitute for good programming! LOL
Of course, but these appear to be coming from third-party components. I hunted down one that was leaking 3-7mb each time a form was closed.
Hope this helps. Tell us what you think of it if you use it.
Are you calling .Dispose() (or .Close()) on forms, etc., when they're not needed?
Shhhhh. Be vewy vewy qwiet. I hunting a dot net memowy weak
Fog Creek Home