ANTS Memory Profiler 8.0 release notes
Published 10 September 2013
October 2nd, 2013
- Profile unmanaged memory allocations called from .NET code, and see information about unmanaged memory usage on the Summary, Class list, and Instance list.
For more information, see Checking unmanaged memory usage.
Re-run recent profiling sessions and open recent profiler results with the new startup page, matching the startup page in ANTS Performance Profiler 8.
The process of setting up a profiling session has also been simplified.
- Compare snapshots from the Summary, with the redesigned largest classes section showing change in size between snapshots.
See how much unmanaged memory is associated with .NET classes and instances. Instances associated with the same unmanaged memory are visually linked.
- The Working set - private performance counter, which is the performance counter used by Windows Task Manager, has been added to the timeline.
- MP-564 - Upgrading the profiler no longer re-installs the J# and C++ redistributable.
- MP-962 - Can now display performance counters with translated/localized names on the timeline.
- MP-1704 - Running Visual Studio add-in as administrator, and launching the profiler as a normal user, no longer raises an IsolatedStorageException.
- MP-1725 - The profiler no longer crashes when trying to profile an x64 exe on an x86 system.
- MP-1888 - IIS always starts under the correct version of .NET, allowing some users who couldn't profile at all before to profile.
- MP-2112 - Profiling an XBAP on Windows Server 2003, using Internet Explorer 6 or 7, gives a "page cannot be displayed" page.
This is because incorrect parameters, including the "-debug", are passed to iexplore.exe when profiling starts.
Workaround: Once you've started profiling and Internet Explorer has loaded, remove the "-debug" from the URL.
- MP-2058 - Cannot profile XBAPs using Internet Explorer 10 or later.
Workaround: Profile XBAPs using Internet Explorer 8 or 9.
- Profiling unmanaged memory is unavailable in Windows XP / Server 2003 and earlier, and for .NET 1.1 applications.