Don't use base::MessageLoop::{Quit,QuitClosure} in remoting/

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 af90692eaefcf5ea136498aef265041bd9cbb4e3..42aa7a01b611533f8663e7a15b472276b8ca830a 100644
--- a/remoting/client/jni/chromoting_jni_runtime.cc
+++ b/remoting/client/jni/chromoting_jni_runtime.cc
@@ -195,8 +195,8 @@ ChromotingJniRuntime::ChromotingJniRuntime() {
   ui_loop_->Start();
 
   // TODO(solb) Stop pretending to control the managed UI thread's lifetime.
-  ui_task_runner_ = new AutoThreadTaskRunner(ui_loop_->task_runner(),
-                                             base::MessageLoop::QuitClosure());
+  ui_task_runner_ = new AutoThreadTaskRunner(
+      ui_loop_->task_runner(), base::MessageLoop::QuitWhenIdleClosure());
   network_task_runner_ = AutoThread::CreateWithType("native_net",
                                                     ui_task_runner_,
                                                     base::MessageLoop::TYPE_IO);