| commit | 08961e988c34af9ee516fddce99b88ddbbec71a9 | [log] [tgz] |
|---|---|---|
| author | nhiroki@chromium.org <nhiroki@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | Tue Aug 13 09:30:11 2013 |
| committer | nhiroki@chromium.org <nhiroki@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | Tue Aug 13 09:30:11 2013 |
| tree | 7ce8a6c2c795f90ba858c094b7df314df438024e | |
| parent | ad907cab8a57d73110eec0b75c8e8376497d39a2 [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