Consider adding analysis of retaining path of objects to memory debugging skill #1224
Description
Is your feature request related to a problem? Please describe.
Consider adding analysis of retaining path of objects to memory debugging skill. This path is often very useful for finding the culprit of the leak.
E.g., if retainers reach back to internals it may show platform leaks. If retainers show a transition to an attached DOM tree, then that's where a cache of some sort is held.
Describe the solution you'd like
This is a follow up from I think this is probably left for follow up work as I am not sure the external tools are capable of doing this programatically.
Describe alternatives you've considered
We can leave as-is and see if this is sufficient.
Additional context
No response