Fix TaskScheduler initialization in remoting processes.

remoting/client/jni/chromoting_jni_runtime.cc

Index: remoting/client/jni/chromoting_jni_runtime.cc
diff --git a/remoting/client/jni/chromoting_jni_runtime.cc b/remoting/client/jni/chromoting_jni_runtime.cc
index c5816538ed1fe6d767f2b5a34bf89ddd901e0dd1..201683ea6c0572ec8d7c8810fd77c4530c774bd3 100644
--- a/remoting/client/jni/chromoting_jni_runtime.cc
+++ b/remoting/client/jni/chromoting_jni_runtime.cc
@@ -111,6 +111,10 @@ ChromotingJniRuntime::~ChromotingJniRuntime() {
       FROM_HERE, base::Bind(&ChromotingJniRuntime::DetachFromVmAndSignal,
                             base::Unretained(this), &done_event));
   done_event.Wait();
+
+  // Block until tasks blocking shutdown have completed their execution.

[fdoray, 2017/02/08 13:22:44]

See https://cs.chromium.org/chromium/src/base/task_scheduler/task_traits.h?l=41

+  base::TaskScheduler::GetInstance()->Shutdown();
+
   base::android::LibraryLoaderExitHook();
   base::android::DetachFromVM();
 }