-
-
Notifications
You must be signed in to change notification settings - Fork 672
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
Tracy-instrumented application crashes in Tracy's static intializers when started through RenderDoc #71
Comments
Sorry, I can't reproduce this. On my side RenderDoc is able to correctly launch a profiled application. Have you tried compiling your program with |
|
Sure, I can take a look. |
I sent you a mail with a link to my OneDrive. |
Closing, as a workaround exists. |
When I try to start my game, which is instrumented using tracy, in RenderDoc, the game instantly crashes due to a static variable of Tracy's moodycamel queue failing to initialize. The actual violation is a nullptr dereference inside a critical section of malloc.
This is a bug that seems to be the result of some weird interaction and the tool RenderDoc: I originally thought this was an issue with RenderDoc, and reported it, but the maintainer pointed out to me that this is actually a crash in my application (see the issue at RenderDoc's Github for details).
The stacktrace shows that the crash happens, when malloc tries to take a lock duing the initialization of a ProducerToken inside of Tracy:
The maintainer of RenderDocs guess on the bug is the following:
Now. I don't really know if this a bug in your code, or moodycamels, or even MSVC C++ library, but since you have comments in TracyProfiler.cpp that mention binary sections and initialization just above the code in question (lines 974 and 975) I hope that you might know how to fix this.
I am on tracy version 0.7
If you need to repro the issue, I can send you my application+renderdoc and instructions on how to repro. It should take only a couple of minutes.
The text was updated successfully, but these errors were encountered: