Analyzing memory leaks

You can detect memory management problems at the class and object level by collecting heap information in heap dumps as your application runs, and then comparing the heap dumps. This comparison identifies changes in the memory that is allocated in the Java heap, and is the basis for generating a list of the most probable leak candidates.

The following topics provide specific instructions:

Obtaining heap dumps for memory leak analysis
Begin leak analysis by capturing heap dumps during a profiling run.

Generating a list of leak candidates
You can automatically generate a list of leak candidates based on two heap dumps.

Identifying memory leaks
The memory leak analysis views identify the objects that are likely to be leaked memory. This information allows you to correct your code and fix the leak.

Saving leak analysis data
You can export a list of leak candidates to html files. You can also save all leak analysis data, including heap dumps, in files for use in Profiling and Logging views.

 

Parent topic

Detecting and analyzing run-time problems

 

Related concepts

Memory leak analysis user interface reference

 

Related tasks

Getting started: Creating a profiling configuration for run-time problem determination

Related information
Getting started: Profiling J2EE applications
Getting started: Memory leak analysis