Important notions are
toolbar button
If a snapshot has already been taken, it will be discarded after confirmation. If the current session is detached, it is not possible to take a new snapshot, Taking a snapshot may take from a few seconds to a few minutes depending on the heap size of the profiled application.
A bookmark will be added when a heap snapshot is taken manually.
Note that you can also use a trigger and the "Trigger heap dump" action to take a snapshot. This is especially useful for offline profiling.
toolbar button
You can calculate the retained size and the deep size of the entire object set by clicking on the "Calculate retained and deep sizes" hyperlink in the title area. Once the calculation is finished, the hyperlink is replaced with the results. This action is not available for the initial set of all objects where the shallow size is equivalent to the retained and deep sizes.
You can create a new object set with the objects that are retained by the current object set by clicking on the "Use retained objects" hyperlink in the title area. Retained objects are all objects that would be garbage collected if the entire current object set would be removed from memory. This always includes the current object set itself. This action is not available for the initial set of all objects where the set of retained objects and the current object set are the same.
The history of your selection steps can be shown at the bottom by clicking on the the corresponding
toolbar button
The heap walker knows which objects have been allocated since the last heap dump or the last invocation of the
mark heap action.
If there was a previous heap dump or a mark heap dump invocation, the title area of the heap walker shows the new instance count and two links titled "Use new" and "Use old" that allow you to select either the instances that have been allocated since that point in time, or the surviving instances that were allocated before. This information is available for each object set, so you can drill down first and select new or old instances later on.
In addition there are two more views:
The view is chosen either
The title area of the heap walker displays several sizes for single objects or object sets. All sizes include only the object data, they do not include internal JVM structures for classes, nor do they include class data or local variables.
history controls of the heap walker in JProfiler's toolbar allow
you to go backward and forward in the history of your view changes.
View changes where selection steps were performed, as well as those performed through
the view selector are recorded in the history.