From b2615c3a1f7e69d99711c0d6edf725a40a7b05ea Mon Sep 17 00:00:00 2001 From: rockot Date: Fri, 19 Feb 2016 11:49:01 -0800 Subject: Mojo: Simplify IPC initialization assumptions ScopedIPCSupport most likely has something wrong with it. This removes all of its complexity since it's no longer needed. Instead only a single ScopedIPCSupport per process is allowed. The ScopedIPCSupport is removed from content::ChannelInit (which can be removed in a future patch) and the one in BrowserMainLoop is initialized a bit earlier, torn down a bit later. BUG=587807 Review URL: https://codereview.chromium.org/1710823003 Cr-Commit-Position: refs/heads/master@{#376517} --- mojo/edk/test/scoped_ipc_support.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'mojo/edk/test/scoped_ipc_support.h') diff --git a/mojo/edk/test/scoped_ipc_support.h b/mojo/edk/test/scoped_ipc_support.h index 132ed44..e920265 100644 --- a/mojo/edk/test/scoped_ipc_support.h +++ b/mojo/edk/test/scoped_ipc_support.h @@ -40,8 +40,7 @@ class ScopedIPCSupportHelper { } // namespace internal // A simple class that calls |InitIPCSupport()| on construction and -// |ShutdownIPCSupport()| on destruction (or |ShutdownIPCSupportOnIOThread()| -// if destroyed on the I/O thread). +// |ShutdownIPCSupport()| on destruction. class ScopedIPCSupport : public ProcessDelegate { public: explicit ScopedIPCSupport( -- cgit v1.1