search

wolfpld / tracy

Frame profiler
https://tracy.nereid.pl/
Other
9.24k stars 640 forks source link

Tracy doesn't open on windows 11 #862

Closed utkusaglm closed 2 days ago

utkusaglm commented 3 weeks ago

Hi, I downloaded the recent release and I cannot open the tracy-profiler. The window closes itself after I open it. The previous release v0.10.0 works fine.

VladimirAndreevich commented 3 weeks ago

I have the same problem on Windows 10

nitrix commented 3 weeks ago

I have the same problem (v0.11.0 but on W10) and was trying to collect more information before opening an issue. Glad it's not just me. v0.10.0 works fine here (@utkusaglm I assuming you meant the previous v0.10.0 not v0.9.1?).

Running the program in cmd.exe gives no information. In MinGW, it claims it's a segmentation fault.

GDB points out the problem but the symbols aren't there to relay what's what.

I was suspecting AVX2 (which my computer doesn't support) but looking at the sources, it seems I would've seen a MessageBoxA if that was the case.

I also tried compiling Tracy myself to investigate, but it complained about MSVC flags, even though I had CMake configured for Clang and Ninja, very weird. If someone is willing to provide a debug build, I could provide stack traces.

atlv24 commented 3 weeks ago

Same here, 0.11 segfaults on win 11

utkusaglm commented 3 weeks ago

@nitrix Yes, my mistake. It is v.10.0 not v0.9.1

nitrix commented 1 week ago

Seems solved for me on W10 with 0.11.1 now :)

wolfpld commented 1 week ago

Seems solved for me on W10 with 0.11.1 now :)

Have you installed the up-to-date MSVC Redist package in the meantime? Or updated your installation of MSVC (at least to 17.10)?

nitrix commented 1 week ago

Looks like that's what it is. I installed CUDA and it installed more recent MSVC redist packages. image

So I'm assuming what happened is the requirements for Tracy increased and I didn't have the newer runtimes then.

EDIT: Ran 0.11.0 just to confirm and that works too now, yeah.

wolfpld commented 1 week ago

Well then, this is "not a bug" and "by design", according to Microsoft.

https://developercommunity.visualstudio.com/t/Visual-Studio-17100-Update-leads-to-Pr/10669759?sort=newest

shafeng commented 4 days ago

I had the same problem, but after I installed the latest vc_redist this problem was solved.

latest vc_redist website: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170