[Chromoting] Introducing refcount-based life time management of the message loops in the service (d…

remoting/host/chromoting_host_context_unittest.cc

Index: remoting/host/chromoting_host_context_unittest.cc
diff --git a/remoting/host/chromoting_host_context_unittest.cc b/remoting/host/chromoting_host_context_unittest.cc
index 1ceb95ca9fa991939aa4b880421a801396cb92f5..a4e670fba68b7464da63e0b522a867664fc3a6be 100644
--- a/remoting/host/chromoting_host_context_unittest.cc
+++ b/remoting/host/chromoting_host_context_unittest.cc
@@ -4,6 +4,7 @@
 
 #include "base/message_loop.h"
 #include "base/message_loop_proxy.h"
+#include "remoting/base/auto_thread_task_runner.h"
 #include "remoting/host/chromoting_host_context.h"
 #include "testing/gtest/include/gtest/gtest.h"
 
@@ -13,7 +14,8 @@ namespace remoting {
 // operates properly and all threads and message loops are valid.
 TEST(ChromotingHostContextTest, StartAndStop) {
   MessageLoopForUI message_loop;
-  ChromotingHostContext context(base::MessageLoopProxy::current());
+  ChromotingHostContext context(new AutoThreadTaskRunner(
+      base::MessageLoopProxy::current()));
 
   context.Start();
   EXPECT_TRUE(context.network_task_runner());