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

Revert of Remove a Platform::current() check from Mojo's error handler in WebSocket (patchset #1 id:1 of https://codereview.chromium.org/2276433003/ )

Reason for revert:
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().

Original issue's description:
> 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}

TBR=yhirano@chromium.org
BUG=637949, 639244
Committed: https://crrev.com/43cf914949a06e8fe3292ca60c5bf046e8a87cc9
Cr-Commit-Position: refs/heads/master@{#416487}

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

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

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

Description was changed from

==========
Revert of Remove a Platform::current() check from Mojo's error handler in
WebSocket (patchset #1 id:1 of https://codereview.chromium.org/2276433003/ )

Reason for revert:
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().


Original issue's description:
> 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}

TBR=yhirano@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=637949,639244
==========

to

==========
Revert of Remove a Platform::current() check from Mojo's error handler in
WebSocket (patchset #1 id:1 of https://codereview.chromium.org/2276433003/ )

Reason for revert:
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().


Original issue's description:
> 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}

TBR=yhirano@chromium.org
BUG=637949,639244
NOTRY=true
==========

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

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2016-09-05 00:29:47]

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-09-05 00:39:41]

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

[commit-bot: I haz the power, 2016-09-05 00:39:42]

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

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

Description was changed from

==========
Revert of Remove a Platform::current() check from Mojo's error handler in
WebSocket (patchset #1 id:1 of https://codereview.chromium.org/2276433003/ )

Reason for revert:
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().


Original issue's description:
> 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}

TBR=yhirano@chromium.org
BUG=637949,639244
NOTRY=true
==========

to

==========
Revert of Remove a Platform::current() check from Mojo's error handler in
WebSocket (patchset #1 id:1 of https://codereview.chromium.org/2276433003/ )

Reason for revert:
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().


Original issue's description:
> 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}

TBR=yhirano@chromium.org
BUG=637949,639244
==========

[haraken, 2016-09-05 00:50:16]

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2016-09-05 00:50:22]

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-09-05 01:05:56]

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

[commit-bot: I haz the power, 2016-09-05 01:05:57]

Try jobs failed on following builders:
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[haraken, 2016-09-05 01:08:06]

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2016-09-05 01:08:15]

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-09-05 02:25:56]

Description was changed from

==========
Revert of Remove a Platform::current() check from Mojo's error handler in
WebSocket (patchset #1 id:1 of https://codereview.chromium.org/2276433003/ )

Reason for revert:
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().


Original issue's description:
> 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}

TBR=yhirano@chromium.org
BUG=637949,639244
==========

to

==========
Revert of Remove a Platform::current() check from Mojo's error handler in
WebSocket (patchset #1 id:1 of https://codereview.chromium.org/2276433003/ )

Reason for revert:
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().


Original issue's description:
> 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}

TBR=yhirano@chromium.org
BUG=637949,639244
==========

[commit-bot: I haz the power, 2016-09-05 02:25:57]

Committed patchset #3 (id:60001)

[commit-bot: I haz the power, 2016-09-05 02:27:53]

Description was changed from

==========
Revert of Remove a Platform::current() check from Mojo's error handler in
WebSocket (patchset #1 id:1 of https://codereview.chromium.org/2276433003/ )

Reason for revert:
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().


Original issue's description:
> 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}

TBR=yhirano@chromium.org
BUG=637949,639244
==========

to

==========
Revert of Remove a Platform::current() check from Mojo's error handler in
WebSocket (patchset #1 id:1 of https://codereview.chromium.org/2276433003/ )

Reason for revert:
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().

Original issue's description:
> 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}

TBR=yhirano@chromium.org
BUG=637949,639244

Committed: https://crrev.com/43cf914949a06e8fe3292ca60c5bf046e8a87cc9
Cr-Commit-Position: refs/heads/master@{#416487}
==========

[commit-bot: I haz the power, 2016-09-05 02:27:54]

Patchset 3 (id:??) landed as
https://crrev.com/43cf914949a06e8fe3292ca60c5bf046e8a87cc9
Cr-Commit-Position: refs/heads/master@{#416487}