cc: Handle future timebases properly in DelayBasedTimeSource
commita0cde48611957ee986f313f5b417342a43e58d3b
authorbrianderson@chromium.org <brianderson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 15 Aug 2013 01:22:04 +0000 (15 01:22 +0000)
committerbrianderson@chromium.org <brianderson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 15 Aug 2013 01:22:04 +0000 (15 01:22 +0000)
treea6ef861683df65d3031dcc7e840deca2cef6c8ef
parent91032424a197a5a9d81c335f3367436f758dbbf3
cc: Handle future timebases properly in DelayBasedTimeSource

The existing code didn't anticipate negative values for
intervals_elapsed, which would round up towards 0 instead
of down towards 0 and cause the next frame to be posted
more than 1 vsync away.

This primarly cropped up on Windows machines, but only
for certain configurations.

BUG=262437

Review URL: https://chromiumcodereview.appspot.com/22887010

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217723 0039d316-1c4b-4281-b951-d872f2087c98
cc/scheduler/delay_based_time_source.cc
cc/scheduler/delay_based_time_source_unittest.cc