See Observatory -> DevTools Tracking Issue.
It's currently very difficult to keep track of which sample frame node is a parent of other nodes when stacks are very deep (e.g., Flutter widget trees):
We should consider adding some sort of guidelines (not necessarily always visible / emphasized), similar to those found in Observatory's CPU profile page:
See Observatory -> DevTools Tracking Issue.
It's currently very difficult to keep track of which sample frame node is a parent of other nodes when stacks are very deep (e.g., Flutter widget trees):
We should consider adding some sort of guidelines (not necessarily always visible / emphasized), similar to those found in Observatory's CPU profile page: