22 Sep
2025
22 Sep
'25
11:26 p.m.
To ensure QueryPerformanceFrequency happens before QueryPerformanceCounter in another thread.
Why? To account for a possible failure mode where [Rtl]QueryPerformanceFrequency and [Rtl]QueryPerformanceCounter are both detoured by an app/system DLL which is order sensitive to either call.
You could say "no known apps have done that" but I don't really see what's wrong with preemptly defending against possible race situation, especially since (1) they are hard to debug, and (2) fixing it doesn't introduce extra complexity other than a stronger memory order.