I once debugged an issue in another process on Windows that would only appear when Chrome was not running. Not sure if Chrome still always does it, but back th

I once debugged an issue in another process on Windows that would only appear when Chrome was not running. Not sure if Chrome still always does it, but back then it was because Chrome changed timer tick frequency to presumably 1 ms by calling timeBeginPeriod (https://msdn.microsoft.com/en-us/library/windows/desktop/dd757624(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/dd7...). On Windows, this affects whole system timer resolution and caused problematic timing code in the other process to function correctly. Funny enough, earlier workaround was to only run this piece of software with a Chrome window open.