The continue window is owned by the desktop environment now.

remoting/host/plugin/host_script_object.h

 // 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.
 
 #ifndef REMOTING_HOST_PLUGIN_HOST_SCRIPT_OBJECT_H_
 #define REMOTING_HOST_PLUGIN_HOST_SCRIPT_OBJECT_H_
 
 #include <string>
 #include <vector>
 
 #include "base/compiler_specific.h"
+#include "base/memory/ref_counted.h"
 #include "base/memory/scoped_ptr.h"
-#include "base/memory/ref_counted.h"
 #include "base/memory/weak_ptr.h"
+#include "base/string16.h"
 #include "base/synchronization/cancellation_flag.h"
 #include "base/synchronization/lock.h"
 #include "base/synchronization/waitable_event.h"
-#include "base/string16.h"
+#include "base/thread_task_runner_handle.h"
 #include "base/threading/platform_thread.h"
 #include "base/threading/thread.h"
 #include "base/time.h"
 #include "remoting/base/auto_thread_task_runner.h"
 #include "remoting/host/chromoting_host_context.h"
 #include "remoting/host/log_to_server.h"
 #include "remoting/host/plugin/host_plugin_utils.h"
 #include "remoting/host/setup/daemon_controller.h"
 #include "remoting/host/ui_strings.h"
 #include "remoting/jingle_glue/xmpp_signal_strategy.h"
@@ skipping 221 matching lines @@
 
   // Set an exception for the current call.
   void SetException(const std::string& exception_string);
 
   //////////////////////////////////////////////////////////
   // Plugin state variables shared between It2Me and Me2Me.
 
   NPP plugin_;
   NPObject* parent_;
   scoped_refptr<AutoThreadTaskRunner> plugin_task_runner_;
+  base::ThreadTaskRunnerHandle plugin_task_runner_handle_;

[Sergey Ulanov, 2013/04/04 21:04:26]

Awesome. Does this work properly? I remember there were some problems with
adding it here. Specifically if you use component build then libbase.so is
shared between chrome and plugin, which means ThreadTaskRunnerHandle DCHECKs
when you try to initialize it in the plugin - it's already initialized in chrome
for regular MessageLoop that runs on that thread. Maybe that problem is not
worth worrying about: it should still be possible to test component plugin
builds in statically-compiled chrome.
Also I'm not sure why you need this here - the timers in ContinueWindow should
run on the UI thread anyway.

[alexeypa (please no reviews), 2013/04/06 18:07:56]

Nope. :-( It breaks when Chrome and Chromoting shared the same base.dll. What do
you think about the patch #3 as we the way to fix it? 
The UI thread is the plugin thread.

 
   // True if we're in the middle of handling a log message.
   bool am_currently_logging_;
 
   ScopedRefNPObject log_debug_info_func_;
 
   //////////////////////////////////////////////////////////
   // It2Me host state.
 
   // Internal implementation of the It2Me host function.
@@ skipping 35 matching lines @@
   // Used to cancel pending tasks for this object when it is destroyed.
   base::WeakPtrFactory<HostNPScriptObject> weak_factory_;
   base::WeakPtr<HostNPScriptObject> weak_ptr_;
 
   DISALLOW_COPY_AND_ASSIGN(HostNPScriptObject);
 };
 
 }  // namespace remoting
 
 #endif  // REMOTING_HOST_PLUGIN_HOST_SCRIPT_OBJECT_H_