.NET Memory Profiler 3.0.113 Released
We recently released a minor maintenance release for .NET Memory Profiler 3.0 - v3.0.113.
It can be downloaded from http://memprofiler.com/download.aspx.
This release only contains a single fix, related to profiling WPF applications under a 64-bit OS. For some reason the dispose tracker caused an error when injecting code in a WPF assembly. And this error only occured when running under a 64-bit OS. Luckily, we had previously written another “code injector” which used another approach for code injection. I believe the implementation of the new “injector” is better, but we never included it, since the old one seemed to work OK (don’t fix it unless it’s broken?), and we wanted to perform some additional testing before replacing. Anyway, now we have replaced it and everything seems to be working OK; even for WPF applications under 64-bit Windows.
July 12th, 2007 at 22:00
Andreas, I was glad to find your blog. I currently use the your profiler (slightly older version) and was glad to see that you are adding a feature to help with unmanaged resources. I’ve been trying to track down an unmanaged leak for some time. I’m using vendor A’s dll, which is supposed to be all managed code, but it calls vendor B’s dll, which is unmanaged. So I’m having a hard time determining whether the leak is in A’s code or in B’s. I downloaded the test version of the latest profiler but still didn’t have quite enough information (or didn’t know how to interpret it, which is the hard part, I think).
August 16th, 2007 at 14:57
I’m sorry for the late reply. I am new to Wordpress and it seems like it’s not perfectly configured yet, so I missed your comment.
Anyway, I think the unmanaged resource tracker in .NET Memory Profiler 3.0 should be able to help you identify what’s causing the excessive unmanaged memory usage. If you need more help, send an e-mail to support@scitech.se, or add a post to our forum at http://memprofiler.com/forum.