chromium/src
0
Fork 0
Code Activity

Remove unnecessary tear down logic from the zygote.

Browse Source 
This CL removes the function TearDownAfterLastChild, because it appears
to be unnecessary. The zygote cleans up its children once it receives
an EOF on it's IPC socket, so once the Browser exits, so will the zygote.

BUG=569191

Review URL: https://codereview.chromium.org/1559983002

Cr-Commit-Position: refs/heads/master@{#367385}
This commit is contained in:
kerrnel
2016-01-04 14:19:11 -08:00
committed by Commit bot
parent 15b37ad2cd
commit 81a34db5d3
1 changed files with 0 additions and 4 deletions

4
content/browser/browser_main_loop.cc

@ -1040,10 +1040,6 @@ void BrowserMainLoop::ShutdownThreadsAndCleanUp() {
}
#endif
#if defined(OS_POSIX) && !defined(OS_MACOSX) && !defined(OS_ANDROID)
ZygoteHostImpl::GetInstance()->TearDownAfterLastChild();
#endif // defined(OS_POSIX) && !defined(OS_MACOSX) && !defined(OS_ANDROID)
// The device monitors are using |system_monitor_| as dependency, so delete
// them before |system_monitor_| goes away.
// On Mac and windows, the monitor needs to be destroyed on the same thread