Remove a Platform::current() check from Mojo's error handler in WebSocket

Remove a Platform::current() check from Mojo's error handler in WebSocket

The check was added in https://codereview.chromium.org/2258003003/
but is no longer needed because I already removed blink::shutdown
from renderer's shutdown sequence.

BUG=637949, 639244
Committed: https://crrev.com/9a8f5c73b4158495cf3e35aee83e1e2b2fc7cb9c
Cr-Commit-Position: refs/heads/master@{#415196}

[haraken, 2016-08-24 07:18:25]

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

[haraken, 2016-08-24 07:18:40]

haraken@chromium.org changed reviewers:
+ yhirano@chromium.org

[haraken, 2016-08-24 07:18:41]

PTAL

[commit-bot: I haz the power, 2016-08-24 07:18:49]

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

[yhirano, 2016-08-24 07:22:30]

lgtm

Is the shutdown change stable? I thought about removing the check after the
branch point in case that CL is reverted.

[haraken, 2016-08-24 07:25:48]

> Is the shutdown change stable? I thought about removing the check after the
> branch point in case that CL is reverted.

Sure, I'll land this after M54's cut.

[commit-bot: I haz the power, 2016-08-24 09:13:47]

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

[commit-bot: I haz the power, 2016-08-24 09:13:48]

Dry run: This issue passed the CQ dry run.

[haraken, 2016-08-29 21:10:12]

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2016-08-29 21:49: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-08-30 06:03:55]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-30 06:06:10]

Description was changed from

==========
Remove a Platform::current() check from Mojo's error handler in WebSocket

The check was added in https://codereview.chromium.org/2258003003/
but is no longer needed because I already removed blink::shutdown
from renderer's shutdown sequence.

BUG=637949
==========

to

==========
Remove a Platform::current() check from Mojo's error handler in WebSocket

The check was added in https://codereview.chromium.org/2258003003/
but is no longer needed because I already removed blink::shutdown
from renderer's shutdown sequence.

BUG=637949

Committed: https://crrev.com/9a8f5c73b4158495cf3e35aee83e1e2b2fc7cb9c
Cr-Commit-Position: refs/heads/master@{#415196}
==========

[commit-bot: I haz the power, 2016-08-30 06:06:11]

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

[haraken, 2016-09-05 00:27:38]

Description was changed from

==========
Remove a Platform::current() check from Mojo's error handler in WebSocket

The check was added in https://codereview.chromium.org/2258003003/
but is no longer needed because I already removed blink::shutdown
from renderer's shutdown sequence.

BUG=637949

Committed: https://crrev.com/9a8f5c73b4158495cf3e35aee83e1e2b2fc7cb9c
Cr-Commit-Position: refs/heads/master@{#415196}
==========

to

==========
Remove a Platform::current() check from Mojo's error handler in WebSocket

The check was added in https://codereview.chromium.org/2258003003/
but is no longer needed because I already removed blink::shutdown
from renderer's shutdown sequence.

BUG=637949,639244

Committed: https://crrev.com/9a8f5c73b4158495cf3e35aee83e1e2b2fc7cb9c
Cr-Commit-Position: refs/heads/master@{#415196}
==========

[haraken, 2016-09-05 00:29:10]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2312573002/ by haraken@chromium.org.

The reason for reverting is: I'll revert r413430 and its dependent CLs because
r413430 caused issue 642072.

The problem is that we cannot simply remove blink::shutdown because the
following scenario can happen:

1) blink::shutdown is not called. Workers are still running.
2) RenderThreadImpl gets destructed. MessageLoop gets destructed.
3) The workers may access the RenderThreadImpl and MessageLoop.

To fix the problem, we need to call ProcessDied() and forcibly kill the renderer
process at the end of RenderThreadImpl::Shutdown().
.