Fix TaskScheduler initialization in remoting processes.

remoting/host/setup/me2me_native_messaging_host_main.cc

Index: remoting/host/setup/me2me_native_messaging_host_main.cc
diff --git a/remoting/host/setup/me2me_native_messaging_host_main.cc b/remoting/host/setup/me2me_native_messaging_host_main.cc
index 70eaa02af7e7c585390e631b54a5942bbafd3e81..f94b2c5ea2c9292a7f82e3be99ae5c95c69cad22 100644
--- a/remoting/host/setup/me2me_native_messaging_host_main.cc
+++ b/remoting/host/setup/me2me_native_messaging_host_main.cc
@@ -269,6 +269,10 @@ int Me2MeNativeMessagingHostMain(int argc, char** argv) {
 
   // Run the loop until channel is alive.
   run_loop.Run();
+
+  // Block until tasks blocking shutdown have completed their execution.
+  base::TaskScheduler::GetInstance()->Shutdown();
+
   return kSuccessExitCode;
 }