commit | b7116c3a9f5f007cfc4313afac85d6ab2dbf02ff | [log] [tgz] |
---|---|---|
author | nhiroki@chromium.org <nhiroki@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | Tue Aug 13 18:30:11 2013 +0900 |
committer | Qijiang Fan <fqj@google.com> | Thu Jun 04 15:04:34 2020 +0900 |
tree | 486e52a31305e27f850f5dc2b65d2603c06066bf | |
parent | 4b3fba706461f199238ac45f17ce71324ae8b897 [diff] |
Revert 217172 "Enable high resolution time for TimeTicks::Now on..." There is a suspicion that this might break some tests: MessageLoopTest.PostDelayedTask_InPostOrder_2, StatsTableTest.StatsCounterTimer TimeTicks.Deltas http://build.chromium.org/p/chromium.win/builders/XP%20Tests%20%282%29/builds/30128 http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/21737 > Enable high resolution time for TimeTicks::Now on Windows Canary > > This should be unnoticeable, except for improved resolution in places such as window.performance.now(). > > The feature is enabled if the user is running Canary channel or has manually specified the --enable-high-resolution-time flag. This will only work if the CPU has a non-stop TSC and isn't a broken Athlon processor. UMA data show this is a safe combination. > > The flag is propagated to renderer processes so that they know to enable it too. > > BUG=158234 > > Review URL: https://chromiumcodereview.appspot.com/16896018 TBR=simonjam@chromium.org Review URL: https://codereview.chromium.org/22984005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217226 0039d316-1c4b-4281-b951-d872f2087c98 CrOS-Libchrome-Original-Commit: 08961e988c34af9ee516fddce99b88ddbbec71a9