Obtaining heap dumps for memory leak analysis
Begin leak analysis by capturing heap dumps during a profiling run.
Memory leak analysis is based on memory heap data collected in heap dumps that are captured during a profiling run. You can capture heap dumps either manually or at timed intervals. You can also import heap dumps.
Use the following criteria to decide which approach to use:
- Capture heap dumps manually if your application requires intervention by the user, or if you are looking for leaks in a specific part of the application. This approach allows you to exercise specific transactions in your application between heap dumps.
- Capture timed heap dumps if your application executes without user intervention. This selection generates heap dumps automatically at intervals that you can specify.
- Import heap dumps if it is not convenient to profile your application using the Workbench.
For specific instructions about collecting memory leak analysis data, read the following topics:
Collecting leak detection data with manual heap dumps
Manual heap dumps are captured at your discretion at any time during the profiling run. Capture a heap dump after application warm-up (during which all the class of interest to you are loaded and initialized), and another heap dump after exercising transactions that you suspect of leaking memory.Collecting leak detection data with timed heap dumps
Timed heap dumps are captured at intervals that you can specify in the Memory Leak Analysis - Timed heap dumps profiling set.Importing heap dumps for memory leak analysis
Instead of collecting heap dumps to analyze memory leaks, you can import heap dumps collected outside of the Workbench.
Parent topic
Analyzing memory leaks