Kill worker process by way of a sync IPC message before it cleans up.

content/browser/worker_host/worker_process_host.cc

Index: content/browser/worker_host/worker_process_host.cc
diff --git a/content/browser/worker_host/worker_process_host.cc b/content/browser/worker_host/worker_process_host.cc
index a228f9cf0ebf31c12ff7f4945da061c94cdeebc9..2c75e74fd2799575ff9692036f285fb6e9a54d6b 100644
--- a/content/browser/worker_host/worker_process_host.cc
+++ b/content/browser/worker_host/worker_process_host.cc
@@ -318,6 +318,8 @@ bool WorkerProcessHost::OnMessageReceived(const IPC::Message& message) {
     IPC_MESSAGE_HANDLER(WorkerProcessHostMsg_AllowDatabase, OnAllowDatabase)
     IPC_MESSAGE_HANDLER(WorkerProcessHostMsg_AllowFileSystem, OnAllowFileSystem)
     IPC_MESSAGE_HANDLER(WorkerProcessHostMsg_AllowIndexedDB, OnAllowIndexedDB)
+    IPC_MESSAGE_HANDLER(WorkerProcessHostMsg_ForceKillWorker,
+                        OnForceKillWorkerProcess)
     IPC_MESSAGE_UNHANDLED(handled = false)
   IPC_END_MESSAGE_MAP_EX()
 
@@ -388,6 +390,11 @@ void WorkerProcessHost::OnAllowIndexedDB(int worker_route_id,
       url, name, resource_context_, GetRenderViewIDsForWorker(worker_route_id));
 }
 
+void WorkerProcessHost::OnForceKillWorkerProcess() {
+  base::KillProcess(

[michaeln, 2013/09/17 20:30:37]

Is this the same low level api we use elsewhere to kill child processes (like
from the taskmanager or that fast renderer exit code path)... just checking

+        process_->GetData().handle, RESULT_CODE_NORMAL_EXIT, false);

[Cris Neckar, 2013/11/01 23:26:34]

nit: may want to check process_launched_ == true before this. Not sure if this
can happen before the process launched or what you will get back as the handle
if it does.

[meacer, 2013/11/04 18:38:10]

Done.

+}
+
 void WorkerProcessHost::RelayMessage(
     const IPC::Message& message,
     WorkerMessageFilter* filter,