The number of top-level objects that are shown is limited to 100 by default. You can add more objects with the hyperlink after the last row in the table. The default number of objects can be adjusted in the view settings.
Each object is optionally annotated with an object ID. With this ID, you can check whether two objects are
the same or not. The display of IDs can be switched off the the context menu and the
view settings.
When you open outgoing references and select a reference or a primitive value, the filter uses the selected node as the criterion. Top-level objects that do not have a path of outgoing references such as the selected path, are discarded by the filter.
If a non-primitive value is selected, and you are profiling in live mode, you can
apply a filter with a code snippet. In the script, you can use the object
parameter
to write your filter expression. The objects that are passed to your script are on
the same level as the one that
you have selected. Return true
if the associated top-level object should be retained, otherwise
it will be discarded. If you want to filter repeatedly with the same expression, don't
forget the script history
feature of the script editor.
If you have selected a top-level object, the parameter is only typed if all objects in the current object set have the same class. Also, in that case the result is equivalent to running the custom filter inspection on the current object set.
Alternatively, you can apply a filter by restricting the selected value. If you are profiling
in live mode, you can perform a match against the result of the toString()
method of the selected
objects. If you have selected a reference which is not at the top level, you can also
filter by
null references or non-null references. For primitive values, you can restrict the
value by settings bounds or testing
for equality. All text fields where you can enter values have a drop down list with
a history that is persistent across sessions.
toString()
on all expanded
references in the view and shows the results. If you open more references or add more
references with the
hyperlink at the bottom of the table, those objects will not have their toString()
values
displayed. You will have to click the button again in order to show the missing values.
The reason why this operation is not performed automatically is that calculating toString() values is an expensive operation that invokes Java code in the profiled JVM and may even have unwanted side effects in buggy implementations.
java.lang.Class
objects of the selected instances.
After your selection, the view helper dialog will assist you in choosing the appropriate view for the new object set.