Change List

Changes in version 5.0.6 from 5.0.5

Improvement: each time the profiler UI is launched, it ensures that the profiler agent DLL is properly registered. If automatic registration is not possible for some reason, troubleshooting instructions are provided. Previously, the agent registration was performed only by the installer. If it failed to register the agent e.g. due to lack of privileges, profiling did not work.
Bug fixed: memory profiling: some unicode characters could be incorrectly displayed for string objects (System.String)
Bug fixed: the demo application could not be started from the Welcome screen on machines where .NET Framework 4 was installed but .NET Framework 2-3.5 was not installed

Bug fixed: possible crash when capturing a memory snapshot under certain circumstances

New feature: ability to automatically trigger snapshot capture on event:
- on high memory usage
- periodically
Visual Studio integration: the toolbar button to launch the profiler UI might be missing in localized versions of Visual Studio
Minor UI fixes

New feature: ability to specify advanced startup options to customize some aspects of profiling.
New feature: "Modules" view shows objects grouped by module, i.e. DLL or EXE where their classes have been declared. This helps to estimate memory usage by library. Read more....
Bug fixed: inspection "Sparse arrays" could show incorrect percents for multidimension arrays and arrays of value types
Bug fixed: error on saving memory snapshot index on profiler UI exit could cancel exit
Minor UI fixes

Bug fixed: memory snapshot capture might fail under certain circumstances after profiled application unloaded its modules
Bug fixes in UI

New feature: ability to export basic snapshot views to *.csv, *.txt, *.html via a command line tool. For detail, see "Export with command line tool" here.
Bug fixed: IIS might start without profiling under certain circumstances
Bug fixed: possible exceptions using object allocation recording