https://bugs.winehq.org/show_bug.cgi?id=55786
--- Comment #1 from Esme Povirk madewokherd@gmail.com --- This is set up in a very confusing way IMO: It waits for 1000 ms, rounded up to the next "GetTickCount interval", and counts the number of times WM_TIMER is posted. Which, apparently, is expected to be 100 for a 10 ms timer. So in order to figure out the difference *in interval* we have to divide 1000 ms by the count, which (for 86), gets us an interval of ~11.6 ms. So I guess this has to do with high system load, where it's not able to handle the timeouts fast enough.
I'm trying to figure out if there's a way to measure that doesn't have this problem. There probably isn't.