[Remoting Android] JniGlDisplayHandler calls invalidate() on UI thread

remoting/client/jni/jni_client.cc

Index: remoting/client/jni/jni_client.cc
diff --git a/remoting/client/jni/jni_client.cc b/remoting/client/jni/jni_client.cc
index 2e16fca968655504946e9e5e7bd86e951fdd6205..d000d38e51c61c6f7c925e046ac0d0439fef8ab2 100644
--- a/remoting/client/jni/jni_client.cc
+++ b/remoting/client/jni/jni_client.cc
@@ -10,7 +10,6 @@
 #include "jni/Client_jni.h"
 #include "remoting/client/jni/chromoting_jni_instance.h"
 #include "remoting/client/jni/chromoting_jni_runtime.h"
-#include "remoting/client/jni/display_updater_factory.h"
 #include "remoting/client/jni/jni_gl_display_handler.h"
 #include "remoting/client/jni/jni_pairing_secret_fetcher.h"
 #include "remoting/client/jni/jni_touch_event_data.h"
@@ -75,8 +74,7 @@ void JniClient::DisconnectFromHost() {
                                                 secret_fetcher_.release());
   }
   if (display_handler_) {

[Hzj_jie, 2016/09/13 19:32:12]

You do not need to do this check, unique_ptr will do it for you.

[Yuwei, 2016/09/13 20:49:40]

Oops... Forgot that.

Done.

-    runtime_->display_task_runner()->DeleteSoon(FROM_HERE,
-                                                display_handler_.release());
+    display_handler_.reset();
   }
 }