commit | 05399593156ef3b8d96933258cd32fe716f63461 | [log] [tgz] |
---|---|---|
author | fmeawad <fmeawad@chromium.org> | Tue Aug 26 20:10:45 2014 |
committer | Commit bot <commit-bot@chromium.org> | Tue Aug 26 20:12:51 2014 |
tree | 78a2765a70904253a57f46a95fa03c78dafc860f | |
parent | 07aef0e93387ef992facfdb9c22716a400f85c46 [diff] |
We have noticed a clock shift when QPC was deployed. It shows as a regression on the perf bots https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=chromium-rel-win8-dual&tests=startup.warm.dirty.blank_page%2Fwindow_display_time&rev=286928 It is not a real regression, the initial_time and initial_ticks are not properly initialized when switching to HighResolution (i.e. QPC). This CL initializes the now_function to the HighResNowWrapper instead of setting it to RolloverProtectedNow then to the HighResNowWrapper. By doing that, we avoid getting an incorrect initial_time and initial_ticks using the RolloverProtectedNow and avoid having to reinitialize. BUG=158234 Review URL: https://codereview.chromium.org/446203002 Cr-Commit-Position: refs/heads/master@{#291974}