Feature Request Reference traversal (finding the root)

When clicking a reference in the "All Of Memory" tab, you see a table to the right "Referenced By". If you click one of the items in that table, you get more information about that object, including how many objects are referencing it. However, you cannot see what those references actually are.

My suggestion is that you can somehow traverse the references, so in a chain of references, you'd be able to find the root object. This could as simple as a button, selecting the currently selected reference, making it the "main" selection (as if it was clicked in the main view) and showing its references.

 

I'll be honest, I was testing the memory profiler in my 2021.3 project, and that wasn't the latest memory profiler. However, I did try memory profiler in a newer project so I can have a later version, but I'm not making that much sense of it atm, so I'm not sure I can provide useful feedback.

Take this for example:

Code (CSharp):

1. public class ReferenceTest : MonoBehaviour
2. {
3.     public TesterA a;
4.  
5.     // Start is called before the first frame update
6.     void Start()
7.     {
8.         a = new TesterA();
9.         var b = new TesterB();
10.         var c = new TesterC();
11.  
12.         a.b = b;
13.         b.c = c;
14.         b.a = a;
15.  
16.         var b2 = new TesterB();
17.         a.b2 = b2;
18.         c.test = this;
19.     }
20. }
21.  
22. public class TesterA
23. {
24.     public TesterB b;
25.     public TesterB b2;
26. }
27.  
28. public class TesterB
29. {
30.     public TesterC c;
31.     public TesterA a;
32. }
33.  
34. public class TesterC
35. {
36.     public ReferenceTest test;
37. }

If I add ReferenceTest monobehavior to an object, play the scene, capture it in memory profiler and then search for "tester", I'm not getting what I'm excepting:



I was under the impression that each field in the "All of memory" view was an instance, but in that case there is one instance missing, since there are two TesterB instances. Furthermore, selecing any of the instances will not show the parent reference class, and every referenced to is empty which is not correct either.

Maybe I'm not using it correctly but this is not making sense to me.

I also noticed that of you put all the classes in the same file, you wouldn't be able to search for the tester classes at all.