In Chrome, we always let content launch child processes, and as such have
no need for ChildProcessHost's synchronization logic. Furthermore, we use
ChildProcessHost on the main thread where such logic is illegal.
This updates ChildProcessHost to be more Chrome-friendly.
BUG=591209,591190
TBR=ben@chromium.org
Review URL: https://codereview.chromium.org/1754003002
Cr-Commit-Position: refs/heads/master@{#378649}
CrOS-Libchrome-Original-Commit: 1a4ffc89ec7416f2ccc69d7e5a74e5ab2f30ab66
2 files changed