The view can show unexpected memory references which prevent garbage collection. The view can then show the new generation objects that were not garbage collectible after that application activity. You can see and explore data structures by following references between objects. For example, a list will manifest itself as a linear succession of links between objects of the same type. A tree will show up explicitly, and it will be easy to tell whether it's balanced or not.
Class objects reveal references from static members.
The trace must contain object reference information. To record this information, issue one of the object reference snapshot commands during trace creation . Then issue a Ctrl-Brk dr command after the target activity completes to take the snapshot of references. The Object Histogram view also offers the ability to examine and explore object references, and it is much simpler to use in that regard. But it is far less powerful than this view because it does not summarize references, and they tend to be scattered among far-flung objects.