Memory Leak Detection & Memory Diagnosis
Detecting a memory leak using heap monitoring
Profile and analyze your Java and .NET application’s memory usage to easily detect
and resolve memory leaks, heavy garbage collector activity and high memory usage
causing stability, performance and scalability problems using dynaTrace Diagnostics’
built-in application memory diagnostics features:
- Heap Monitoring
- Total Heap Dump
- Selective Memory Dump
Monitor the memory behaviour of your applications over time to understand trends
early on and detect memory leaks before they cause “out of memory” problems and
correlate this information to response times.
Isolating the classes/objects causing the memory leak using a total heap dump
Apply Total Heap Dumps to further triage your memory issues and to understand object
hierarchies down to individual objects. Take multiple snapshots over time to understand
the exact object types (classes) that are using too much memory and isolate the
individual objects that directly or indirectly hold reference to those objects that
are responsible for the ever-growing memory usage.
Root cause analysis under full production load using a selective memory dump
Finally, use “selective memory dumps” even under full production load where regular
profilers cannot be used anymore to understand at which point in your transaction
execution (PurePath) the previously identified objects are created. This way, you
can easily analyze if all references to these objects have been cleared as anticipated
so that the Garbage Collector can free the memory once it is no longer needed.
E.g., you may determine that a specific “Purchase” transaction has allocated 5,000
"Product" objects, which are also referenced by another application component and
thus their allocated memory has never been freed up, causing a memory leak that
results in a long-term, cumulative stability issue.
Read more about...
|