Revert of Remove WTF::isShutdown()

Revert of Remove WTF::isShutdown() (patchset #1 id:1 of https://codereview.chromium.org/2277663002/ )

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 WTF::isShutdown()
>
> Now it's unused.
>
> BUG=639244
>
> Committed: https://crrev.com/47f9c2d1ca781e1e4df5dc05b74200a6ba696afe
> Cr-Commit-Position: refs/heads/master@{#414030}

TBR=yutak@chromium.org
BUG=639244
NOTRY=true

Committed: https://crrev.com/2302bf7e2cf6bbaa8f6b43a966acebbe974b43b9
Cr-Commit-Position: refs/heads/master@{#416481}

[haraken, 2016-09-05 00:30:11]

Created Revert of Remove WTF::isShutdown()

[haraken, 2016-09-05 00:30:26]

Description was changed from

==========
Revert of Remove WTF::isShutdown() (patchset #1 id:1 of
https://codereview.chromium.org/2277663002/ )

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 WTF::isShutdown()
> 
> Now it's unused.
> 
> BUG=639244
> 
> Committed: https://crrev.com/47f9c2d1ca781e1e4df5dc05b74200a6ba696afe
> Cr-Commit-Position: refs/heads/master@{#414030}

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

to

==========
Revert of Remove WTF::isShutdown() (patchset #1 id:1 of
https://codereview.chromium.org/2277663002/ )

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 WTF::isShutdown()
> 
> Now it's unused.
> 
> BUG=639244
> 
> Committed: https://crrev.com/47f9c2d1ca781e1e4df5dc05b74200a6ba696afe
> Cr-Commit-Position: refs/heads/master@{#414030}

TBR=yutak@chromium.org
BUG=639244
NOTRY=true
==========

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

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2016-09-05 00:32:04]

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:35:32]

Description was changed from

==========
Revert of Remove WTF::isShutdown() (patchset #1 id:1 of
https://codereview.chromium.org/2277663002/ )

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 WTF::isShutdown()
> 
> Now it's unused.
> 
> BUG=639244
> 
> Committed: https://crrev.com/47f9c2d1ca781e1e4df5dc05b74200a6ba696afe
> Cr-Commit-Position: refs/heads/master@{#414030}

TBR=yutak@chromium.org
BUG=639244
NOTRY=true
==========

to

==========
Revert of Remove WTF::isShutdown() (patchset #1 id:1 of
https://codereview.chromium.org/2277663002/ )

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 WTF::isShutdown()
> 
> Now it's unused.
> 
> BUG=639244
> 
> Committed: https://crrev.com/47f9c2d1ca781e1e4df5dc05b74200a6ba696afe
> Cr-Commit-Position: refs/heads/master@{#414030}

TBR=yutak@chromium.org
BUG=639244
NOTRY=true
==========

[commit-bot: I haz the power, 2016-09-05 00:35:33]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-09-05 00:38:25]

Description was changed from

==========
Revert of Remove WTF::isShutdown() (patchset #1 id:1 of
https://codereview.chromium.org/2277663002/ )

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 WTF::isShutdown()
> 
> Now it's unused.
> 
> BUG=639244
> 
> Committed: https://crrev.com/47f9c2d1ca781e1e4df5dc05b74200a6ba696afe
> Cr-Commit-Position: refs/heads/master@{#414030}

TBR=yutak@chromium.org
BUG=639244
NOTRY=true
==========

to

==========
Revert of Remove WTF::isShutdown() (patchset #1 id:1 of
https://codereview.chromium.org/2277663002/ )

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 WTF::isShutdown()
>
> Now it's unused.
>
> BUG=639244
>
> Committed: https://crrev.com/47f9c2d1ca781e1e4df5dc05b74200a6ba696afe
> Cr-Commit-Position: refs/heads/master@{#414030}

TBR=yutak@chromium.org
BUG=639244
NOTRY=true

Committed: https://crrev.com/2302bf7e2cf6bbaa8f6b43a966acebbe974b43b9
Cr-Commit-Position: refs/heads/master@{#416481}
==========

[commit-bot: I haz the power, 2016-09-05 00:38:26]

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