Get the call stack trace(s) in the UI

[rben-dev]

Is your feature request related to a problem? Please describe.
Sorry if I missed this, but the --stacks command line toggle activates stack traces collection (which can be indeed found in the produced json file), but nothing in the UI seems to relate to this.

Describe the solution you'd like
Get a view of the most significant (in the sense of CPU/GPU/memory usage) call trace(s) when hovering over a line or a function.

Additional context
When profiling a rather complex code where a line (e.g. a constructor of a class) is called multiple times in multiple contexts, it can be difficult to spot the call trace leading to the "hot spot" (consuming the most CPU/GPU/memory). I might however have missed a way of dealing with such situations (?)

[FergusFettes]

I'm think I'm looking for the same thing: maybe this works for you?

https://github.com/joerick/pyinstrument

[mcarans]

Having the stack trace in the UI would be really useful. I tried pyinstrument but it uses too much memory when profiling my application.