Fix a bug that could occasionaly cause setInterval to stop

components/scheduler/renderer/throttled_time_domain.cc

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "components/scheduler/renderer/throttled_time_domain.h"
 
 #include "base/time/tick_clock.h"
 
 namespace scheduler {
 
 ThrottledTimeDomain::ThrottledTimeDomain(TimeDomain::Observer* observer,
                                          base::TickClock* tick_clock)
     : VirtualTimeDomain(observer, tick_clock->NowTicks()),
       tick_clock_(tick_clock) {}
 
 ThrottledTimeDomain::~ThrottledTimeDomain() {}
 
-base::TimeTicks ThrottledTimeDomain::ComputeDelayedRunTime(
-    base::TimeTicks,
-    base::TimeDelta delay) const {
-  // We ignore the |time_domain_now| parameter since its the virtual time but we
-  // need to use the current real time when computing the delayed runtime.  If
-  // don't do that, throttled timers may fire sooner than expected.
-  return tick_clock_->NowTicks() + delay;
+base::TimeTicks ThrottledTimeDomain::BlinkNow() const {

[rmcilroy, 2016/07/18 13:03:03]

As discussed offline, could we see whether it is possible to use the real time
always for throttled task queues to avoid having to add this new API?

[alex clarke (OOO till 29th), 2016/07/18 15:02:01]

Done.

+  // Report the real time to Blink.
+  return tick_clock_->NowTicks();
 }
 
 const char* ThrottledTimeDomain::GetName() const {
   return "ThrottledTimeDomain";
 }
 
 }  // namespace scheduler