Open eyesoftime opened 3 months ago
Possibly related: #875 #879.
Can you check if the fix in #879 fixes your issue?
I hope I managed to test it against the correct revision but so far the issue seems to persist. After a short run the program dies with the Segmentation Fault message. Sometimes not even that much. Testing with gcc-14.2.0. FWIW, compiling it with clang has been producing a working program.
I hope I managed to test it against the correct revision but so far the issue seems to persist. After a short run the program dies with the Segmentation Fault message. Sometimes not even that much. Testing with gcc-14.2.0. FWIW, compiling it with clang has been producing a working program.
Thanks for testing! Your issue sounded similar to mine. By the way, making a full Debug build of the profiler proved very useful. Seeing a stack trace of the crash, or simply having asserts enabled was really useful.
I'm using Tracy with a C++ program on MSYS2/UCRT gcc compiler on Win10 and I'm running consistently into a crash when I want to time the async calls that run in separate threads. I know the platform is not probably ideal but it is what I'm using right now. I've tried to distill it down to the reproducible case and I think I've managed to do that for my own machine. It links Tracy statically and to run Tracy I've also had to link my program with
dbghelp
andws2_32
. I've read the section ondbghelp
and I've also tried to provide locking mechanism and use dlls but (after a lot of fiddling around) that does not eliminate the crash for me. Toggling delayed init and manual lifetime management doesn't change the situation either. It seems to be a segmentation fault. Sometimes it manages to pick up connection with Tracy server. When using dynamic libraries it tends to crash even before the connection is established or just after.It's worth noting that if Tracy zone markup is removed from within the async lambda the program runs to the end. It also works when the number of parallel async calls is reduced from 10 to 1. What I noticed is that it seems to run fine with up to 6 threads, starts occasionally crashing with 7, and almost definitely crashes with 8. The machine I'm using has 8 cores so perhaps there's something about that.
I can't track it deeper into Tracy as I don't have that much expertise with the language. So apart from submitting this issue I can only ask a couple of questions. Am I trying to use Tracy in an unsupported manner? Is it the platform that I'm using? Is it something I can fix on my side?