[Remoting Android] Releases |secret_fetcher_| in DisconnectFromHost()

[Remoting Android] Releases |secret_fetcher_| in DisconnectFromHost()

In some situations the same JniClient will be used for multiple connections
where ConnectToHost()->DisconnectFromHost()->ConnectToHost() will be called.

In ConnectToHost() we DCHECK !secret_fetcher_ but don't release it in
DisconnectFromHost(), which fails the DCHECK.

This CL solves this problem by resetting |secret_fetcher_| in
DisconnectFromHost(). However, we still need to investigate why JniClient
is being used for multiple connections.

BUG=617471
Committed: https://crrev.com/909aa6b2ac08abe5d75cdb5050c979c29ef451e3
Cr-Commit-Position: refs/heads/master@{#398085}

[Yuwei, 2016-06-06 18:06:41]

yuweih@chromium.org changed reviewers:
+ lambroslambrou@chromium.org

[Yuwei, 2016-06-06 18:06:41]

PTAL

[Lambros, 2016-06-06 18:13:54]

The CQ bit was checked by lambroslambrou@chromium.org

[Lambros, 2016-06-06 18:13:55]

lgtm

[commit-bot: I haz the power, 2016-06-06 18:14:21]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2046663002/1

[commit-bot: I haz the power, 2016-06-06 19:18:13]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-06 19:20:00]

Description was changed from

==========
[Remoting Android] Releases |secret_fetcher_| in DisconnectFromHost()

In some situations the same JniClient will be used for multiple connections
where ConnectToHost()->DisconnectFromHost()->ConnectToHost() will be called.

In ConnectToHost() we DCHECK !secret_fetcher_ but don't release it in
DisconnectFromHost(), which fails the DCHECK.

This CL solves this problem by resetting |secret_fetcher_| in
DisconnectFromHost(). However, we still need to investigate why JniClient
is being used for multiple connections.

BUG=617471
==========

to

==========
[Remoting Android] Releases |secret_fetcher_| in DisconnectFromHost()

In some situations the same JniClient will be used for multiple connections
where ConnectToHost()->DisconnectFromHost()->ConnectToHost() will be called.

In ConnectToHost() we DCHECK !secret_fetcher_ but don't release it in
DisconnectFromHost(), which fails the DCHECK.

This CL solves this problem by resetting |secret_fetcher_| in
DisconnectFromHost(). However, we still need to investigate why JniClient
is being used for multiple connections.

BUG=617471

Committed: https://crrev.com/909aa6b2ac08abe5d75cdb5050c979c29ef451e3
Cr-Commit-Position: refs/heads/master@{#398085}
==========

[commit-bot: I haz the power, 2016-06-06 19:20:01]

Patchset 1 (id:??) landed as
https://crrev.com/909aa6b2ac08abe5d75cdb5050c979c29ef451e3
Cr-Commit-Position: refs/heads/master@{#398085}