Move throttling of background timers into the renderer scheduler

components/scheduler/base/virtual_time_domain.cc

 // Copyright 2015 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/base/virtual_time_domain.h"
 
 #include "base/bind.h"
 #include "components/scheduler/base/task_queue_impl.h"
 #include "components/scheduler/base/task_queue_manager_delegate.h"
 
@@ skipping 26 matching lines @@
   return false;
 }
 
 void VirtualTimeDomain::AsValueIntoInternal(
     base::trace_event::TracedValue* state) const {}
 
 void VirtualTimeDomain::AdvanceTo(base::TimeTicks now) {
   base::AutoLock lock(lock_);
   DCHECK_GE(now, now_);
   now_ = now;
+  DCHECK(task_queue_manager_delegate_);
+
+  LazyNow lazy_now(now_);
+  WakeupReadyDelayedQueues(&lazy_now);

[Sami, 2015/11/24 12:48:48]

Isn't the DoWork going to do this? Why do it twice?

[alex clarke (OOO till 29th), 2015/11/25 12:29:36]

Seems it isn't needed.  It definitely was at one stage however.

   task_queue_manager_delegate_->PostTask(FROM_HERE, do_work_closure_);
 }
 
 const char* VirtualTimeDomain::GetName() const {
   return "VirtualTimeDomain";
 }
 
 }  // namespace scheduler