Fix leaks in mojo::edk::NodeController

Fix leaks in mojo::edk::NodeController

There are a few instances where the broker process (e.g. the browser in
process Chrome) tracks some state -- including outgoing messages --
pertaining to a client process connection. In some cases this tracked data
is not cleaned up once the client process is disconnected. This fixes that.

BUG=704938
Review-Url: https://codereview.chromium.org/2780433003
Cr-Commit-Position: refs/heads/master@{#460001}
Committed: https://chromium.googlesource.com/chromium/src/+/69726f4ba3947fd4ddbfb07fd9f1a596289cdae9

[Ken Rockot(use gerrit already), 2017-03-28 00:37:03]

The CQ bit was checked by rockot@chromium.org to run a CQ dry run

[Ken Rockot(use gerrit already), 2017-03-28 00:37:34]

rockot@chromium.org changed reviewers:
+ yzshen@chromium.org

[Ken Rockot(use gerrit already), 2017-03-28 00:37:34]

Hi Yuzhu, would you mind taking a quick look at this?

[commit-bot: I haz the power, 2017-03-28 00:37:35]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[yzshen1, 2017-03-28 00:49:36]

LGTM

[Ken Rockot(use gerrit already), 2017-03-28 00:50:17]

The CQ bit was unchecked by rockot@chromium.org

[Ken Rockot(use gerrit already), 2017-03-28 00:50:19]

The CQ bit was checked by rockot@chromium.org

[commit-bot: I haz the power, 2017-03-28 00:50:25]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-28 01:30:19]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-28 01:30:20]

Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Ken Rockot(use gerrit already), 2017-03-28 02:12:15]

The CQ bit was checked by rockot@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-03-28 02:12:33]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Ken Rockot(use gerrit already), 2017-03-28 02:49:33]

Description was changed from

==========
Fix leaks in mojo::edk::NodeController

There are a few instances where the broker process (e.g. the browser in
process Chrome) tracks some state (including outgoing messages)
pertaining to some external process connection. In some cases this
tracked data is not cleaned up once the process is disconnected. This
fixes that.

BUG=704938
==========

to

==========
Fix leaks in mojo::edk::NodeController

There are a few instances where the broker process (e.g. the browser in
process Chrome) tracks some state -- including outgoing messages --
pertaining to a client process connection. In some cases this tracked data
is not cleaned up once the client process is disconnected. This fixes that.

BUG=704938
==========

[Ken Rockot(use gerrit already), 2017-03-28 02:50:04]

Patchset #1 (id:1) has been deleted

[Ken Rockot(use gerrit already), 2017-03-28 03:06:18]

The CQ bit was unchecked by rockot@chromium.org

[Ken Rockot(use gerrit already), 2017-03-28 03:06:20]

The CQ bit was checked by rockot@chromium.org

[Ken Rockot(use gerrit already), 2017-03-28 03:06:20]

The patchset sent to the CQ was uploaded after l-g-t-m from yzshen@chromium.org
Link to the patchset: https://codereview.chromium.org/2780433003/#ps20001
(title: ".")

[commit-bot: I haz the power, 2017-03-28 03:06:23]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-28 03:38:33]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1490670380289920,
"parent_rev": "4ea301f06b3c94bc2cf9a8be6ca151e3c01987ba", "commit_rev":
"69726f4ba3947fd4ddbfb07fd9f1a596289cdae9"}

[commit-bot: I haz the power, 2017-03-28 03:39:16]

Description was changed from

==========
Fix leaks in mojo::edk::NodeController

There are a few instances where the broker process (e.g. the browser in
process Chrome) tracks some state -- including outgoing messages --
pertaining to a client process connection. In some cases this tracked data
is not cleaned up once the client process is disconnected. This fixes that.

BUG=704938
==========

to

==========
Fix leaks in mojo::edk::NodeController

There are a few instances where the broker process (e.g. the browser in
process Chrome) tracks some state -- including outgoing messages --
pertaining to a client process connection. In some cases this tracked data
is not cleaned up once the client process is disconnected. This fixes that.

BUG=704938

Review-Url: https://codereview.chromium.org/2780433003
Cr-Commit-Position: refs/heads/master@{#460001}
Committed:
https://chromium.googlesource.com/chromium/src/+/69726f4ba3947fd4ddbfb07fd9f1...
==========

[commit-bot: I haz the power, 2017-03-28 03:39:17]

Committed patchset #1 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/69726f4ba3947fd4ddbfb07fd9f1...