Win should call ::TerminateProcess to exit a renderer process

content/renderer/render_thread_impl.cc

 // Copyright (c) 2012 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 "content/renderer/render_thread_impl.h"
 
 #include <algorithm>
 #include <limits>
 #include <map>
 #include <utility>
@@ skipping 930 matching lines @@
   // In a multi-process mode, we immediately exit the renderer.
   // Historically we had a graceful shutdown sequence here but it was
   // 1) a waste of performance and 2) a source of lots of complicated
   // crashes caused by shutdown ordering. Immediate exit eliminates
   // those problems.
   //
   // In a single-process mode, we cannot call _exit(0) in Shutdown() because
   // it will exit the process before the browser side is ready to exit.
   if (!base::CommandLine::ForCurrentProcess()->HasSwitch(
           switches::kSingleProcess))
-    _exit(0);
+    base::Process::Current().TerminateCurrentProcessImmediately(0);

[Primiano Tucci (use gerrit), 2017/01/17 07:55:16]

No need for current() here 

 }
 
 bool RenderThreadImpl::ShouldBeDestroyed() {
   DCHECK(base::CommandLine::ForCurrentProcess()->HasSwitch(
       switches::kSingleProcess));
   // In a single-process mode, it is unsafe to destruct this renderer thread
   // because we haven't run the shutdown sequence. Hence we leak the render
   // thread.
   //
   // In this case, we also need to disable at-exit callbacks because some of
@@ skipping 1459 matching lines @@
   }
 }
 
 void RenderThreadImpl::OnRendererInterfaceRequest(
     mojom::RendererAssociatedRequest request) {
   DCHECK(!renderer_binding_.is_bound());
   renderer_binding_.Bind(std::move(request));
 }
 
 }  // namespace content