Skip to content

Conversation

jmagnuson
Copy link

One of a number of potential solutions for #265, this PR simply adds awareness to custom perf supplying a PID set, to avoid the issues I mentioned in the ticket.

Related: #95

@djc
Copy link
Contributor

djc commented May 26, 2025

This PR seems to provide a way to run flamegraph without setting a workload, which seems like a convoluted way of enabling a time limit. How about we add an explicit --sleep (or something) option to flamegraph it self, instead?

(Sorry for the delay in responding.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants