.NET and Memory

Today we released a maintenance version of .NET Memory Profiler. If you are profiling .NET 1.x applications, or if you are profiling ASP.NET applications on a system with .NET 4.0 installed, it is highly recommended that you download this release. The previous installer was missing a file which caused problems with the dispose tracker when profiling .NET 1.x applications. More importantly, the previous version didn’t detect the Web development server (WebDev.WebServer) included with .NET 4.0. This version detects both version 2.0 and 4.0 of WebDev.WebServer and allows you to select which one to use when profiling an ASP.NET application. For more information about this release, and other maintenance releases, please read the release notes. The latest version can be downloaded from the download page.

Yesterday we published a maintenance release of .NET Memory Profiler 3.5 (version 3.5.130). This release contains several important fixes, so it is recommended that you download an install this release if you have an older version installed. For instance, due to refactorings in the previous release, native stack walking failed to use symbols from the Microsoft symbol store, which caused the native allocation call stacks to be much less detailed. We have also improved the performance when working with very large snapshots, and the memory usage has been reduced somewhat. Still, to avoid out of memory problems, it is recommended that the 64-bit version of .NET Memory Profiler is used when profiling applications with high memory usage. The 64-bit version is automatically used when the standalone profiler is used on a 64-bit operating, but since Visual Studio is a 32-bit process, the integrated profiler will only run as 32-bit.

The latest release can be downloaded from the Download page, and more information about the release is available in the release notes.

Finally! Last week we launched .NET MemoryProfiler 3.5. It has taken a while to finish this version, but I’m very pleased with the result. For more information about this version, and to download it, please visit the .NET Memory Profiler site.

It took much longer than planned, but now we have released .NET Memory Profiler 3.5 Beta. It contains significant improvement over the preview, such as a call stack reducer, significantly faster loading and saving of session files, the possibility to ignore analysis issues and support for .NET Framework 4.0. This beta is more or less feature complete and we expect to release the final version of .NET Memory Profiler 3.5 before the end of September. For more information about the beta and to download it, please visit the beta page at http://memprofiler.com/beta. If you have any comments about the new version, you can comment in this blog, or send an e-mail to memprofiler@scitech.se.

We didn’t quite make it within two weeks as I wrote in my last post, but now .NET Memory Profiler 3.5 Preview has been released. For more information and to download the preview, visit the .NET Memory Profiler 3.5 Preview page. If you have any comments, questions, or bug reports, we would like to hear about them. Please send any feedback you have to memprofiler@scitech.se.

Today we released a minor maintenance release of .NET Memory Profiler 3.1 (v3.1.321). This release can be downloaded from the .NET Memory Profiler download page. For more information about changes and fixes in this release, check out the release notes.

A more interesting release is the upcoming release of .NET Memory Profiler 3.5. We have put a lot of work into this version and I hope that you will feel that it is a significant improvement over v3.1. Finishing version 3.5 has taken quite a bit longer than we orginally planned, mainly because we started to include features that were initially intended for v4.0. Anyway, it’s soon here. A preview should be available within two weeks. More information will follow, and I really intend to start writing more posts for this blog.

Last week we released a maintenance version of .NET Memory Profiler 3.1. The most important update in this version is support for .NET Framework 3.5 SP1. Due to some low-level changes in the runtime, some parts of the profiler didn’t work correctly, in particular the “attach-to” feature and memory dump import.

The new version can be downloaded from http://memprofiler.com/download.aspx. For additional information about what’s new in this release, check the release notes.

Earlier today we released .NET Memory Profiler 3.1.301. This release contains a few fixes related to ASP.NET profiling and the resource tracker. We also recently released .NET Memory Profiler 3.1.297, which contains more significant improvements and fixes to more serious problems. For more information about the latest releases, see the release notes. To download version 3.1.301, go to the download page at http://memprofiler.com/download.aspx.

Yesterday we released .NET Memory Profiler 3.1.283. This release contains a fix for a problem with memory dump imports and attached processes.

If you use the profiler to attach to a process or if you import memory dump files, it is highly recommended that you install this release.

It can be downloaded from http://memprofiler.com/download.aspx.

Several other fixes since the release of .NET Memory Profiler 3.1 are also included in this release. See the release notes for more information about all fixes.

Finally. We have now released version 3.1 of .NET Memory Profiler. This version contains several new features and enhancements, such as improved memory assertions, easier navigation of snapshot data, Visual Studio 2008 support, better identification of native memory, and much more. For more information about the new release, visit the .NET Memory Profiler site at http://memprofiler.com.

You can download a fully functional trial of .NET Memory Profiler 3.1 at http://memprofiler.com/download.aspx.