Add support for base::Closure in the MessageLoop.

chrome/renderer/renderer_main.cc

Index: chrome/renderer/renderer_main.cc
diff --git a/chrome/renderer/renderer_main.cc b/chrome/renderer/renderer_main.cc
index 2066dc8e04c1ca0710f83a0f25464db91dc0e85d..4094da25868e370346943e224bc81791d57663f1 100644
--- a/chrome/renderer/renderer_main.cc
+++ b/chrome/renderer/renderer_main.cc
@@ -218,11 +218,11 @@ class RendererMessageLoopObserver : public MessageLoop::TaskObserver {
             1, 3600000, 50, base::Histogram::kUmaTargetedHistogramFlag)) {}
   virtual ~RendererMessageLoopObserver() {}
 
-  virtual void WillProcessTask(const Task* task) {
+  virtual void WillProcessTask(base::TimeTicks time_posted) {
     begin_process_message_ = base::TimeTicks::Now();
   }
 
-  virtual void DidProcessTask(const Task* task) {
+  virtual void DidProcessTask(base::TimeTicks time_posted) {
     if (begin_process_message_ != base::TimeTicks())

[joth, 2011/04/16 15:11:57]

suggest
if (begin_process_message_.is_null())

(also, it looks odd to me passing class TimeTicks by value rather than const
ref, but it seems to be standard practice)

[awong, 2011/04/17 00:34:57]

Ooh...good catch.

As for TimeTicks being passed by value, it's designed to be done that way. The
data member is just one int64, so pass by value ends up more efficient than by
const ref.

On 2011/04/16 15:11:57, joth wrote:

       process_times_->AddTime(base::TimeTicks::Now() - begin_process_message_);
   }