Treat a delay of under 1 millisecond in MessagePumpDefault as a signal that the corresponding delayed task needs to execute
On Windows for e.g. the lowest resolution we can get on the system clock is 1 ms or 4 ms depending on whether the machine
is powered by AC or battery. The OS default is 15ms. So that effectively means that if a delayed task is waiting to execute
for a delay of under 1 ms would cause the underlying OS WaitForSingleObject call to return immediately effectively spinning
a tight loop with a kernel mode context switch.
Fix is to treat a delay of under 1 ms as a signal that the task is ready to execute for all platforms.
BUG=487724
Review URL: https://codereview.chromium.org/1137453006
Cr-Commit-Position: refs/heads/master@{#329997}
1 file changed
