ANTS Memory Profiler 7
Find memory leaks and optimize memory usage in your .NET application
The Summary Screen
The Summary Screen in ANTS Memory Profiler is the fastest way to get an overview of your application's memory usage, and often eliminates the tedious process of digging around for problems.
Use the Summary Screen to:
- Get an overview of memory usage the instant a snapshot is taken.
- Quickly jump to the most likely causes of performance degradation.
- Effortlessly compare memory snapshots against each other.
What can the Summary Screen show me?
- Change in memory usage ‐ Compare the change in memory usage between any pair of snapshots. ANTS Memory Profiler will alert you to increases in memory usage, which can be symptomatic of memory leaks.
- Large Object Heap Fragmention ‐ The .NET Garbage Collector doesn't compact the Large Object Heap, which can lead to memory fragmentation over time. This eventually leads to restrictions on the size of objects which can be allocated, and can result in OutOfMemory exceptions in extreme cases.
- .NET Memory Allocation ‐ Understand where memory has been allocated by the .NET framework. A high proportion of objects in Generation 2 often indicates something is holding onto objects for longer than needed.
- Largest Classes ‐ Instantly visualize which classes are using the most memory, then click on them to jump straight to information on instances of those classes, and to understand whether they really need to exist.
I just wanted to congratulate your team on a job well done, the new tool looks great and the addition of the summary pie charts showing my top 5 consumers for each snapshot was invaluable in quickly focusing my attention on the problem areas.Jeremy Jarrell, Matrix Solutions.
Volume discounts apply.
Try a 14-day fully functional free trial of ANTS Memory Profiler.
I purchased ANTS Profiler as I knew I had a memory leak in my code and I could see this with Task Scheduler. It would have taken me weeks to find the cause but, 2 hours after installing ANTS Profiler, the problem was solved; it paid itself off on the first day I used it.Graeme Elliott, Lead Architect, Spirit Software Solutions