All Objects
-
The all objects view shows the list of all loaded classes together
with the number of instances which are allocated on the heap. This view is only visible
if you profile with Java 1.5 (JVMTI). To see the objects allocated during a certain time period,
and to record allocation call stacks, please use the
recorded objects view.
-
The all objects view has an aggregation level selector. It allows you
to switch between
-
classes
Every row in the table is a single class. This is the default aggregation level.
-
packages
Every row in the table is a single package. Sub-packages are not included. In this
aggregation level, the table becomes a tree table. You can open each package
by clicking on the tree node on its left and see the contained classes directly beneath it.
-
Java EE components
Every row in the table is a Java EE component.
This aggregation level is like a filter for the classes mode and enables you to quickly check the
loaded Java EE components in your profiled application.
-
There are three columns shown in the table, which can be sorted.
-
Name
Depending on the aggregation level, this column shows different values:
-
classes
shows the name of the class or the array type. When using Java version up to 1.4 or Java 1.5 with the old profiling interface JVMPI,
the notation <class>[] stands for non-primitive arrays of any class type.
(e.g. the array might be of type String[] or Object[]).
A further distinction is not possible due to restrictions in the profiling interface.
-
package
shows the name of the package.
-
Java EE
shows the display name of the Java EE component. If the display name is different from the
actual class name, the class name is displayed in square brackets.
-
Instance count
Shows how many instances are currently allocated on the heap. This instance count
is displayed graphically as well.
-
Size
Shows the total size of all allocated instances. Note that this is the
shallow size which does not include the size of referenced arrays and
instances but only the size of the corresponding pointers. The size is in bytes and includes
only the object data, it does not include internal JVM structures for the class, nor does it
include class data or local variables.
-
The update frequency for the all objects view can be set on the
miscellaneous tab
in the profiling settings dialog.
The update frequency of the all objects view is adjusted automatically
according to the total number of objects on the heap. If there are many objects on the heap, the
calculation of the all objects view becomes more expensive, so the update frequency is
reduced. You can always retrieve the current data by clicking on the
refresh button in the status bar.
-
You can add a selected class or package to the
class tracker by
bringing up the context menu with a right click and choosing
Add Selection To Class Tracker. If the class tracker is not recording, recording will
be started for all classes configured in the class tracker. If the class tracker is recording with
a different object type or liveness type, all recorded data will be cleared after a confirmation dialog.