-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGTRAP With Criterion and Flamegraph Features #237
Comments
I also get a sigtrap if the frequency is set too high even without criterion integration |
Here is an exact copy of the code: https://github.com/cedar-policy/cedar-local-agent/blob/main/benches/is_authorized.rs |
I'm getting a SIGTRAP in similar circumstances, with every frequency value |
Did you guys find a way around this? |
I use this: https://github.com/flamegraph-rs/flamegraph. It doesn't have a high sampling frequency though. Wasn't able to resolve that issue. |
Did you set it up with |
There's a CLI arg that you can use to run a criterion benchmark. I used that. |
yes got it. thanks! |
I'm also seeing this, particularly on ARM mac machines - a linux VM seems be run fine. |
I tested this on an M1 Mac pro, so that could be it. |
+1 same issue on M1 mac here |
+1 same issue on M1 mac here, but it only happens when I use Mutex. |
After upgrading to the latest rust version (1.81.0), I managed to get a stack trace for a SIGTRAP. Not sure if its related to this issue, but I filed a new one here: #252 |
I found this crate from this article: https://www.jibbow.com/posts/criterion-flamegraphs/, which it seems you've implemented as the
criterion
feature flag. I've found a bug and tested it on both the example code from the article and thecriterion
feature flag and I'm getting the same issue.Here's the error:
And my code:
I am running with
--profile-time 5
.The text was updated successfully, but these errors were encountered: