diff options
| author | ananta <ananta@chromium.org> | 2015-05-14 17:42:41 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-05-15 00:43:04 +0000 |
| commit | 990d0c7d24a7ef39567875587355637dc9fef122 (patch) | |
| tree | f268d22f960edd5e267692d4f2a083b16f19c453 /content/browser/devtools/protocol/tracing_handler.h | |
| parent | 3619e48edfdfad6683c55992103d89897108783f (diff) | |
| download | chromium_src-990d0c7d24a7ef39567875587355637dc9fef122.zip chromium_src-990d0c7d24a7ef39567875587355637dc9fef122.tar.gz chromium_src-990d0c7d24a7ef39567875587355637dc9fef122.tar.bz2 | |
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}
Diffstat (limited to 'content/browser/devtools/protocol/tracing_handler.h')
0 files changed, 0 insertions, 0 deletions