-
-
Notifications
You must be signed in to change notification settings - Fork 619
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
Negative TscTime triggered assertion #758
Comments
What CPU do you have? Is it a multi-socket machine? |
No, it's just a commerial level laptop with an amd R7 4800u |
That doesn't make much sense. TSC readings should be monotonic. On my 7950, the time between You can compile with |
I recompiled with the flag and the negative values are gone. But the assertion is still failing as |
I tried on a 5800x and it runs without any issue. If you want to investigate more into the problem I'm happy to help. Otherwise feel free to close it. Thank you. |
Using v0.10 on Ubuntu 20.04
Crash site is
tracy/server/TracyWorker.cpp:5031
with this line of code :assert( fd->frames.empty() || fd->frames.back().start <= time );
Reproducible with the following code snippet.
I tried to inspect the issue with gdb and found somehow the call to get
time
on line 5030 (const auto time = TscTime( ev.time );
) gives negative result. Interestingly when I added a sleep before theFrameMark
, it usually takes a bit longer for tracy to crash.The text was updated successfully, but these errors were encountered: