Add ScopedAllowIO in WebrtcTransport when shutting down WebRTC session.

Add ScopedAllowIO in WebrtcTransport when shutting down WebRTC session.

PeerConnection creates new threads internally and shuts them down when
connection is closed. This is a blocking operation, so Debug builds were
DCHECK'ing every time connection is terminated. Added ScopedAllowIO to
work around this issue.

BUG=660081
Committed: https://crrev.com/2c41f984a001aa9f1c686ef2d888fdfa1fcaea23
Cr-Commit-Position: refs/heads/master@{#437711}

[Sergey Ulanov, 2016-12-09 01:52:15]

Patchset #1 (id:1) has been deleted

[Sergey Ulanov, 2016-12-09 01:53:33]

sergeyu@chromium.org changed reviewers:
+ jamiewalch@chromium.org, jochen@chromium.org

[Sergey Ulanov, 2016-12-09 01:53:34]

jochen@, please approve PRESUBMIT.py change
jamiewalch@, please review webrtc_transport.cc

[jochen (gone - plz use gerrit), 2016-12-09 08:26:42]

jochen@chromium.org changed reviewers:
+ jam@chromium.org

[jochen (gone - plz use gerrit), 2016-12-09 08:26:42]

deferring to jam@, master of ScopedAllowIO

[jam, 2016-12-09 17:21:13]

rs lgtm

anyone can add ScopedAllowIO

(I'm more concerned with ScopedAllowWait, which incidentally is what
platformthread should be depending on in this case. I'll file a bug for that).

[Jamie, 2016-12-09 23:07:25]

lgtm

[Sergey Ulanov, 2016-12-09 23:18:07]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2016-12-09 23:19:12]

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, 2016-12-10 01:21:06]

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

[commit-bot: I haz the power, 2016-12-10 01:21:07]

Try jobs failed on following builders:
  chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build
URL)

[Sergey Ulanov, 2016-12-10 01:26:16]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2016-12-10 01:27:19]

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, 2016-12-10 01:45:25]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1481333176121620,
"parent_rev": "486244e9be55fec9daed6111c7cf2e3157db84b9", "commit_rev":
"5df90cbbc817d86fc89cdaa68f3859d85a0e0360"}

[commit-bot: I haz the power, 2016-12-10 01:45:51]

Description was changed from

==========
Add ScopedAllowIO in WebrtcTransport when shutting down WebRTC session.

PeerConnection creates new threads internally and shuts them down when
connection is closed. This is a blocking operation, so Debug builds were
DCHECK'ing every time connection is terminated. Added ScopedAllowIO to
work around this issue.

BUG=660081
==========

to

==========
Add ScopedAllowIO in WebrtcTransport when shutting down WebRTC session.

PeerConnection creates new threads internally and shuts them down when
connection is closed. This is a blocking operation, so Debug builds were
DCHECK'ing every time connection is terminated. Added ScopedAllowIO to
work around this issue.

BUG=660081

Review-Url: https://codereview.chromium.org/2567533002
==========

[commit-bot: I haz the power, 2016-12-10 01:45:52]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2016-12-12 14:59:12]

Description was changed from

==========
Add ScopedAllowIO in WebrtcTransport when shutting down WebRTC session.

PeerConnection creates new threads internally and shuts them down when
connection is closed. This is a blocking operation, so Debug builds were
DCHECK'ing every time connection is terminated. Added ScopedAllowIO to
work around this issue.

BUG=660081

Review-Url: https://codereview.chromium.org/2567533002
==========

to

==========
Add ScopedAllowIO in WebrtcTransport when shutting down WebRTC session.

PeerConnection creates new threads internally and shuts them down when
connection is closed. This is a blocking operation, so Debug builds were
DCHECK'ing every time connection is terminated. Added ScopedAllowIO to
work around this issue.

BUG=660081

Committed: https://crrev.com/2c41f984a001aa9f1c686ef2d888fdfa1fcaea23
Cr-Commit-Position: refs/heads/master@{#437711}
==========

[commit-bot: I haz the power, 2016-12-12 14:59:13]

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