ProtocolPirate
Programmer
I ran the trial versions of Memory Validator and .NET Memory Profiler, but I couldn't get any useful information out of either. I have unmanaged code that I am marshaling data to and from which clearly has leaks, and I also have an OCX for scanning that has even bigger leaks. Whatever happened to good ol' Bounds Checker?