Scitech .Net Memory Profiler 5.0.142 » Developer.Team

Scitech .Net Memory Profiler 5.0.142

Scitech .Net Memory Profiler 5.0.142
Scitech .Net Memory Profiler 5.0.142 | 38 Mb


.NET Memory Profiler is a powerful tool for finding memory leaks and optimizing the memory usage in programs written in C#, VB.NET or any other .NET Language. With the help of the profiling guides, the automatic memory analyzer, and specialized trackers, you can make sure that your program has no memory or resource leaks, and that the memory usage is as optimal as possible.

Even though the .NET runtime has a garbage collector, memory leaks are still a reality. A memory leak occurs when an instance that is no longer needed is still, unintentionally, reachable from a root (e.g. a static field).

By using .NET Memory Profiler you can detect memory leaks long before they are noticed in the Task manager and before they create an out-of-memory error. Even a minor memory leak can cause problems in a long-running program.

Help you identify memory leaks by collecting and comparing snapshots
Snapshots of the memory usage can be collected before and after a user action is performed (e.g. opening and closing a document). Comparing the snapshots will provide information about new instances created by the action. You can then investigate the new instances further to find out whether they are part of a memory leak or not.

Give you information about how the instances were created
To understand why an instance is unintentionally kept alive, it is crucial that you know how it was created, and how other instances in the root path was created. .NET Memory Profiler will present the allocation call stack for each instance in the snapshot.

Native resources, such as Win32 heap memory, window handles, and file handles, are used in a managed .NET program as well. Even though they may not be directly used by your application, they can be indirectly used by the .NET runtime, Windows, and native libraries.

By using .NET Memory Profiler you can make sure that native resources are released as quickly as possible, and that there are no resource leaks.

Provide real-time information about resource allocations and all resource instances
The unmanaged resources tracker will collect information about all native resources and allocations. This information is presented in the real-time view, giving you a good overview of the resource usage of your program.

If your program uses too much memory, performs too many allocations, or has bad allocation patterns, the performance will suffer. This can affect not only your program, but other programs as well. With .NET Memory Profiler you will get the information you need to ensure that the memory usage of your program is as efficient as possible.

Help you optimize memory and resource usage
The heap-utilization tracker will tell you how the managed heaps are used and indicate bad allocation patterns. The dispose tracker will help you make sure that disposable instances are correctly disposed. Together, this information can help you optimize the memory and resource usage of the application.

Detect duplicate instances
The automatic memory analyzer in .NET Memory Profiler will give you detailed information about all duplicated instances. This includes simple duplicates, like duplicated strings, and complex duplicates, such as large identical hashtables. This information will help you avoid unnecessary memory usage caused by the duplicates.

Help you make sure that all instances are correctly disposed
The dispose tracker will give you information about disposable instances that are not correctly disposed. Disposable instances often have finalizers and wrap native resources. Failing to dispose an instance can cause costly finalization and delay the release of a native resource.

Version 5.0.142
Fix: Profiler environment settings was not correctly restored when profiler ASP.NET using IIS and Windows services. This could cause problems with subsequent profiling sessions.
Fix: An unhandled error could be shown if a new type or filter was selected while the instances list was updated.
Fix: Aborting a long running sort on the instances list could prevent future sorting of the instances.
New: Identifying Windows 10 version of Debugging Tools for attach and memory dump import.
Change: Removed dependencies on PsApi.dll and DbgHelp.dll in the profiled process.
Change: Fixed a typo in the interned string analyser.


[/b]

[b] Only for V.I.P
Warning! You are not allowed to view this text.
SiteLock