You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often when doing memory analysis, I like to see a "spider" view of an instance. That is, which instances directly reference my current instance, and which instances are directly referenced by my current instance.
where the parents and children section might contain numerous parents, and each parent and child is clickable and directly makes that instance the current instance. This type of view can often provide information not apparent from other views in MAT (in my experience) since incoming and outgoing references are typically 2 separate views in MAT.
The text was updated successfully, but these errors were encountered:
| --- | --- |
| Bugzilla Link | 272330 |
| Status | NEW |
| Importance | P3 enhancement |
| Reported | Apr 15, 2009 11:11 EDT |
| Modified | Dec 05, 2009 08:42 EDT |
| Reporter | Randall Theobald |
Description
Often when doing memory analysis, I like to see a "spider" view of an instance. That is, which instances directly reference my current instance, and which instances are directly referenced by my current instance.
For example:
parents: 003F41DB 3 105 1 23 java.lang.Object[]
current: 003F1234 4 24 1 1 java.lang.WeakReference
children: 00123454 5 24 1 0 java.lang.Integer
where the parents and children section might contain numerous parents, and each parent and child is clickable and directly makes that instance the current instance. This type of view can often provide information not apparent from other views in MAT (in my experience) since incoming and outgoing references are typically 2 separate views in MAT.
The text was updated successfully, but these errors were encountered: