.NET Memory Profiler 3.0.108 Released
We recently released a maintenance release for .NET Memory Profiler 3.0 - v3.0.108.
It can be downloaded from http://memprofiler.com/download.aspx.
This release contains a few minor fixes, for example:
When unloading an unsaved project from the projects explorer the profiler did not prompt you to save the changes.
There was a timing issue in the profiler that could cause the profiler and the profiled process to get stuck. This happened when identifying root references while collecting a heap snapshot under .NET 1.1. It is normally very unlikely that this should occur; we have only had a single report about this, and yet the problem has probably existed since the first release.
The code that handles side-by-side DLLs in the unmanaged resources tracker contained an error. Fixing this error requires some time, so we have only included a temporary solution in this release. The resource tracker will only track instances that are created by the firstly loaded DLL. This is probably not a big issue, most resource instances will still be tracked correctly, but it might occur in the GdiPlus DLL when working against Microsoft Office components. We are currently working on a better solution.
For more information see the release notes at http://memprofiler.com/releasenotes.htm.
