New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 647659 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

There should be a way to take ownership of a SyncSocket handle

Project Member Reported by maxmorin@chromium.org, Sep 16 2016

Issue description

At present, a SyncSocket always closes its handle. This is a problem for mojo, which always closes the handle it sends over IPC, leading to a double-close. There are also double-close issues in some other cases, like in a test when an IPC call with a handle is intercepted. For example, see MockAudioRendererHost https://cs.chromium.org/chromium/src/content/browser/renderer_host/media/audio_renderer_host_unittest.cc
 
Status: Verified (was: Untriaged)
SyncSocket::Release() does this.

Sign in to add a comment