CoreFoundation socket leak?
CoreFoundation socket leak?
- Subject: CoreFoundation socket leak?
- From: Mike Laster <email@hidden>
- Date: Fri, 25 Oct 2002 18:48:13 -0400
When creating a listening socket using the following call:
socketRef = CFSocketCreateWithSocketSignature(NULL, &signature,
kCFSocketAcceptCallBack, MCFSocketCallback, &socketContext);
if (socketRef != NULL)
{
}
But the bind fails because another process is currently using the port,
the file handle seems to be leaked.
The returned socketRef is NULL, so I can't call CFSocketinvalidate to
clean it up, but lsof shows:
CSPRelay 11408 mlaster 16u inet 0x039cfd1c 0t0 TCP *:*
(CLOSED)
CSPRelay 11408 mlaster 17u inet 0x03887d1c 0t0 TCP *:5678
(LISTEN)
The 16u handle was from a failed attempt, and the 17u handle was from
the second time I called it after freeing up port 5678.
Is this a bug in CoreFoundation, or is there something I need to do to
get rid of sockets that failed to bind?
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.