Timing issue in IncomingTaskQueue::AddToIncomingQueue

base/message_loop/incoming_task_queue.cc

 // Copyright 2013 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 "base/message_loop/incoming_task_queue.h"
 
 #include <limits>
 
 #include "base/location.h"
 #include "base/message_loop/message_loop.h"
@@ skipping 40 matching lines @@
 bool IncomingTaskQueue::AddToIncomingQueue(
     const tracked_objects::Location& from_here,
     const Closure& task,
     TimeDelta delay,
     bool nestable) {
   DLOG_IF(WARNING,
           delay.InSeconds() > kTaskDelayWarningThresholdInSeconds)
       << "Requesting super-long task delay period of " << delay.InSeconds()
       << " seconds from here: " << from_here.ToString();
 
+  PendingTask pending_task(
+    from_here, task, CalculateDelayedRuntime(delay), nestable);
   AutoLock locked(incoming_queue_lock_);
-  PendingTask pending_task(
-      from_here, task, CalculateDelayedRuntime(delay), nestable);
 #if defined(OS_WIN)
   // We consider the task needs a high resolution timer if the delay is
   // more than 0 and less than 32ms. This caps the relative error to
   // less than 50% : a 33ms wait can wake at 48ms since the default
   // resolution on Windows is between 10 and 15ms.
   if (delay > TimeDelta() &&
       delay.InMilliseconds() < (2 * Time::kMinLowResolutionThresholdMs)) {
     ++high_res_task_count_;
     pending_task.is_high_res = true;
   }
@@ skipping 99 matching lines @@
   // After we've scheduled the message loop, we do not need to do so again
   // until we know it has processed all of the work in our queue and is
   // waiting for more work again. The message loop will always attempt to
   // reload from the incoming queue before waiting again so we clear this flag
   // in ReloadWorkQueue().
   message_loop_scheduled_ = true;
 }
 
 }  // namespace internal
 }  // namespace base