We need it back.
Yes it’s slow to open up when you mis-click the tab, put it behind an “Are you sure Bruv?” or something but slap it back in there because the current layout is painfully untraversable in comparison.
Thanks for the feedback Pac-FitXR! I have added it to our feature request list.
Just to make sure we address the right problem: you say that the current view is untraversable in comparison to the treemap. What is, specifically, the most painful thing to you now, compared to how things worked with with the treemap?
Tree map workflow was simpy more human-readable, and the filtering system is really useful for all sorts of measurements that don’t simply narrow down to “Type” and “most used”.
To suggest more functionality: Ability to refresh map view to preview “Filtered data only” would be a nice addition, also some of the existing filters in 0.7.1p1 could use more attention. “Size” could have below/above thresholds as option for example.
The list views are simply less friendly to read. Usable, but meh in comparison/
Thanks Pav-FitXR! Makes sense, I have noted it down ![]()
Is this still in consideration?
Hi @tspk91! Yes, it’s on our plans - I don’t want to promise a release date for it, because we have to change our plans all the time, but I will promise it’s (a) high on that list and (b) we really want to get this back again. Thank you for checking!
Yup, tree view single most useful feature of the memory profiler. Downgraded to 0.7.1-preview.1 to get it back.
Heard. Though note of caution regarding your downgrade: we fixed several issues with the Managed Memory Crawler in the package in the versions since 0.7.x. The Crawler is responsible for finding all alive managed objects in the heap by crawling through all reference chains, starting at the static roots and GCHandles. So the 0.7 version of the package might underreport Managed Objects.
For 2022.2 onwards we also split out Graphics memory from the way we used to report native memory, so it might also gravely underreport native memory. Really, the solution should be that we bring that view back, not that you have to downgrade for it.
Just to add that, been ending up going back to most recent version and after working with it for a while, don’t miss the tree view as much anymore as I thought I would. It’s def a really nice visualization but there’s several improvements to the Unity Objects list that make it quite easy to work in that view instead.
Overall, have to say, really appreciate having the memory profiler. Tool’s a life saver. It’s consistently where the worst sins in our codebase end up being confessed to.
What I miss more than the tree view now is being able to just throw entire sessions away, not just individual snapshots ![]()