New Module: Profile your JUCE UI/dsp performance with Perfetto

unexpected token ‘struct’

Heh, what a troll.

Specifically, juce_Component.cpp

If it’s your first time with Perfetto, I’d definitely recommend just sprinkling the TRACE_COMPONENT around in your own paint methods to get some success with the whole workflow first.

It’s not really “supported” to hack it into the actual JUCE code and expect it to work. That’s part of why I opened this feature request, because being able to officially hook into the paint cycle would make make recording timings and debugging performance WAY easier: FR: Callback or other mechanism for exposing Component debugging/timing

But you can get essentially the same data (with better naming) by peppering the macro in each of your paint calls…

Maybe someone else has ran into the issue? Or to go further off the beaten path you could try checking out an earlier commit, perhaps something in the recent bump to perfetto 41 made this impossible — if you do investigate, let me know if you get it working!