Julien Wajsberg

I feel it's even less discoverable :/

Looping in @tarekziade in this discussion as this is/can be in the scope for his current project and more generally what he thinks of this.

Here is a profile where I invert/uninvert several times: https://perfht.ml/2wfQBxf A lot of time seems to be spent in getCallNodeInfo. I'm trying to confirm from a prod build.

This profile is better: https://perfht.ml/2ydxAsK Especially we spend time in https://github.com/devtools-html/perf.html/blob/a40a1ec19131e2e09821f8ac0b43fc3a3a6d2186/src/profile-logic/profile-data.js#L640 which isn't especially surprising :)

Yes, the tooltips we have now are just for individual markers. The goal here is to analyze several markers together. I believe this idea is broader than just for GC.

I'm not sure this is useful with what we already have. But tell me what you think @mstange @gregtatum @zoepage .

I'm not sure what "heaviest stack trace" means. I think this is a subset of https://github.com/firefox-devtools/profiler/issues/15, especially the first point of what Mike Conley described there. I tried to implement...

We can file individual bugs for the rest of the tasks I outlined above. I think the 3rd task may be done, but the 4th isn't and I still think...

Looks like it's a dupe of #4157 that I filed some time ago.

cc @arroway