Add pause_on_start flag to WorkerProcessMsg_CreateWorker_Params.

content/browser/devtools/worker_devtools_manager.cc

Index: content/browser/devtools/worker_devtools_manager.cc
diff --git a/content/browser/devtools/worker_devtools_manager.cc b/content/browser/devtools/worker_devtools_manager.cc
index 00735f34c2ebfe69744a2fb44fb261bd4b230872..119392dda203c80b34713d7200b395da3c2227fd 100644
--- a/content/browser/devtools/worker_devtools_manager.cc
+++ b/content/browser/devtools/worker_devtools_manager.cc
@@ -236,8 +236,6 @@ void WorkerDevToolsManager::WorkerCreated(
     if (instance.Matches(it->worker_url, it->worker_name,
                          instance.partition(),
                          instance.resource_context())) {
-      worker->Send(new DevToolsAgentMsg_PauseWorkerContextOnStart(
-          instance.worker_route_id()));
       WorkerId new_worker_id(worker->GetData().id, instance.worker_route_id());
       paused_workers_[new_worker_id] = it->old_worker_id;
       terminated_workers_.erase(it);
@@ -282,6 +280,22 @@ void WorkerDevToolsManager::WorkerContextStarted(WorkerProcessHost* process,
   paused_workers_.erase(it);
 }
 
+bool WorkerDevToolsManager::TerminatedWorkerExist(

[yurys, 2014/03/27 08:37:26]

We could merge WorkerCreated into this new method to make it clear why the
worker is now in paused_workers_ map.

[horo, 2014/03/27 09:48:10]

Done.

+    const WorkerProcessHost::WorkerInstance& instance) const {
+  for (TerminatedInspectedWorkers::const_iterator it =
+           terminated_workers_.begin();
+       it != terminated_workers_.end();
+       ++it) {
+    if (instance.Matches(it->worker_url,
+                         it->worker_name,
+                         instance.partition(),
+                         instance.resource_context())) {
+      return true;
+    }
+  }
+  return false;
+}

[kinuko, 2014/03/27 08:04:34]

I think adding pause_on_start param in CreateWorker message makes sense, but
when we move DevToolsManager to solely on UI thread this simple sync method
needs to be handled asynchronously-- will we have an async method like void
TerminatedWorkerExist(const Callback<void(bool)>& callback) in the new
architecture then?

[horo, 2014/03/27 09:45:48]

Done.

+
 void WorkerDevToolsManager::RemoveInspectedWorkerData(
     const WorkerId& id) {
   for (TerminatedInspectedWorkers::iterator it = terminated_workers_.begin();