[Merge M52] Avoid deleting RenderProcessHostImpl for in-process

[Merge M52] Avoid deleting RenderProcessHostImpl for in-process

This is suspected to be the cause of null pointer crash in Android
WebView when RenderProcessHostImpl::FromID unexpectedly returns null.

Issue is RenderProcessHostImpl::DecrementWorkerRefCount does not
check for run_renderer_in_process() like RemoveRoute. Move the check
to beginning of Cleanup instead.

BUG=616476
Review-Url: https://codereview.chromium.org/2029623002
Cr-Commit-Position: refs/heads/master@{#397235}
(cherry picked from commit 55cb5a389f401a539225c7e7b59197114db5cd29)

Committed: https://chromium.googlesource.com/chromium/src/+/53b10adeda96e325d3c1ebdb81bf5a370400999d

[boliu, 2016-06-02 15:40:05]

Description was changed from

==========
[Merge M52] Avoid deleting RenderProcessHostImpl for in-process

This is suspected to be the cause of null pointer crash in Android
WebView when RenderProcessHostImpl::FromID unexpectedly returns null.

Issue is RenderProcessHostImpl::DecrementWorkerRefCount does not
check for run_renderer_in_process() like RemoveRoute. Move the check
to beginning of Cleanup instead.

BUG=616476

Review-Url: https://codereview.chromium.org/2029623002
Cr-Commit-Position: refs/heads/master@{#397235}
(cherry picked from commit 55cb5a389f401a539225c7e7b59197114db5cd29)
==========

to

==========
[Merge M52] Avoid deleting RenderProcessHostImpl for in-process

This is suspected to be the cause of null pointer crash in Android
WebView when RenderProcessHostImpl::FromID unexpectedly returns null.

Issue is RenderProcessHostImpl::DecrementWorkerRefCount does not
check for run_renderer_in_process() like RemoveRoute. Move the check
to beginning of Cleanup instead.

BUG=616476

Review-Url: https://codereview.chromium.org/2029623002
Cr-Commit-Position: refs/heads/master@{#397235}
(cherry picked from commit 55cb5a389f401a539225c7e7b59197114db5cd29)

Committed:
https://chromium.googlesource.com/chromium/src/+/53b10adeda96e325d3c1ebdb81bf...
==========

[boliu, 2016-06-02 15:40:06]

Committed patchset #1 (id:1) manually as
53b10adeda96e325d3c1ebdb81bf5a370400999d.