Commit 6540eb67 authored by sergeyu@chromium.org's avatar sergeyu@chromium.org

Initialize JingleThreadWrapper in the Android client

Previously Android client was crashing because JingleThreadWrapper
was not initialized for the networking thread. It was broken by
crrev.com/271351, which removed JingleThreadWrapper initialization
from  LijbingleTransportFactory.

TBR=lambroslambrou@chromium.org

Review URL: https://codereview.chromium.org/298013004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272905 0039d316-1c4b-4281-b951-d872f2087c98
parent ef306c69
......@@ -8,6 +8,7 @@
#include "base/bind.h"
#include "base/logging.h"
#include "jingle/glue/thread_wrapper.h"
#include "net/socket/client_socket_factory.h"
#include "remoting/client/audio_player.h"
#include "remoting/client/jni/android_keymap.h"
......@@ -314,6 +315,8 @@ void ChromotingJniInstance::ConnectToHostOnDisplayThread() {
void ChromotingJniInstance::ConnectToHostOnNetworkThread() {
DCHECK(jni_runtime_->network_task_runner()->BelongsToCurrentThread());
jingle_glue::JingleThreadWrapper::EnsureForCurrentMessageLoop();
client_context_.reset(new ClientContext(
jni_runtime_->network_task_runner().get()));
client_context_->Start();
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment