| commit | a1731206edb26ee22e0b0e378cbd81203c12a2cd | [log] [tgz] |
|---|---|---|
| author | fmeawad <fmeawad@chromium.org> | Wed Aug 27 05:10:45 2014 +0900 |
| committer | Qijiang Fan <fqj@google.com> | Thu Jun 04 17:25:26 2020 +0900 |
| tree | 532a48a830fa66c06efc4d5d1d7c43856ff3b802 | |
| parent | ae2c406382bd53dc96dfe2717e581fd2e0f7639a [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} CrOS-Libchrome-Original-Commit: 05399593156ef3b8d96933258cd32fe716f63461