| commit | 23373cc799ff355a37f25402c31a22ac773938ec | [log] [tgz] |
|---|---|---|
| author | fmeawad <fmeawad@chromium.org> | Thu Aug 28 09:48:16 2014 +0900 |
| committer | Qijiang Fan <fqj@google.com> | Thu Jun 04 17:26:12 2020 +0900 |
| tree | 0e0fa4fac9c682a407f5d67a7b24f8c6e4ae7969 | |
| parent | 04a196aa2b218b4ab44c6edc97812e5881397f65 [diff] |
Revert of Initialize the now_funciton to the HighResNowWrapper in case High Res is supported (patchset #7 of https://codereview.chromium.org/446203002/) Reason for revert: It causes a Canary crash https://code.google.com/p/chromium/issues/detail?id=408354 The added static initializer causes a crash in libpeerconnetion used by WebRTC Fix to reland: remove static initializer. Original issue's description: > 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 > > Committed: https://chromium.googlesource.com/chromium/src/+/10c40c221c314e41add0a5b4df1ee7467681a430 TBR=jar@chromium.org,willchan@chromium.org,maruel@chromium.org,thakis@chromium.org,jam@chromium.org,cpu@chromium.org NOTREECHECKS=true NOTRY=true BUG=158234 Review URL: https://codereview.chromium.org/516693002 Cr-Commit-Position: refs/heads/master@{#292288} CrOS-Libchrome-Original-Commit: 3a38fb5efd526a2278ab3b577c8c7881a3ad4d20