runtime: Windows "high-resolution" timer seems to do the opposite #51530
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
OS-Windows
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Ran this code on any release post-1.16, on windows:
What did you expect to see?
~200ish ticks over the life of the program
What did you see instead?
64 ticks
Additional:
This works correctly on 1.15.15. Probably seems to be introduced in 1.16 It is important to understand the following:
The new code seems to substitute high-resolution timers in place of setting the timer resolution to 1ms at the start of a program. However, my system timer is already set to 1ms and despite that, go sleeps/ticks/etc. are operating at 15.whatever millisecond resolution on my windows system.
The text was updated successfully, but these errors were encountered: