Memory Leak Detector for VB.NET?

[mike1reynolds]

I ran the trial versions of Memory Validator and .NET Memory Profiler, but I couldn't get any useful information out of either. Whatever happened to good ol' Bounds Checker?

[Plater]

All .NET code has implicit bounds checking. Unless you're using unmanage/unsafe code, DLLImports, other points or graphics, you shouldn't have a memory leak?

[Shashi Sadasivan]

Well, every event handler that is created, is a potential memory leak.
I am not sure if that has been fixed with 3.0/3.5 but certainly exists with 2.0.

You may have to create a custom dispose method and remove the event handlers manually.

Im on my way trying to find how to use .net clr memory profiler, there are a few other paid ones which apparantly show a better result, but then again, if you have used gdb before, they dont really tell you where the leak is occouring, so the profilers are a step ahead and they apparantly do show which objects are still active.

[mike1reynolds]

I'm doing marshaling, but the biggest leaks seem to come from an OCX for scanning that I purchased.

[mike1reynolds]

I found another leak detector, GlowCode, and while I still can't get line numbers, at least I can get the function name where the leaks were allocated. I expected to see leaks in my marshaling code, and sure enough there are, but I'm also getting leaks from calling WNetAddConnection2 in MPR.DLL.

[Plater]

I've never attached more then one event handler to a given event so I didn't even think of that! Yes, the Application events tell you that you need to remove them manually, so I suppose that could be true.