You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visualizing stack traces as flame graphs directly on-device is an interesting approach to reducing the latency between frame drop detection and root cause analysis. Does your implementation use a standard library like py-spy or a custom sampling mechanism to generate the flame graph data structures before rendering them on the UI?
Activity
uidq1290 commentedon May 18, 2022
ideav5 commentedon May 18, 2022
jonahwhite115 commentedon Sep 28, 2026
Visualizing stack traces as flame graphs directly on-device is an interesting approach to reducing the latency between frame drop detection and root cause analysis. Does your implementation use a standard library like
py-spyor a custom sampling mechanism to generate the flame graph data structures before rendering them on the UI?ideav5 commentedon Sep 28, 2026
uidq1290 commentedon Sep 28, 2026