3 ms·
currentTimeMs is Environment.TickCount, which in this case happens to be negative. It's worth noting that GetTickCount() is documented as returning an unsigned
by userbinator 3y ago
currentTimeMs is Environment.TickCount, which in this case happens to be negative.
It's worth noting that GetTickCount() is documented as returning an unsigned count, and unless you really need to time intervals > ~49 days to millisecond accuracy, everything works as expected with modulo arithmetic.
Windows' AppVerifier has an option that causes GTC to rollover much sooner, specifically to test for such bugs.