Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 25246 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The System.Net.Sockets.Socket.Disconnect(bool reuseSocket) method delegates to Disconnect_internal() which is mapped to ves_icall_System_Net_Sockets_Socket_Disconnect_internal() in socket-io.c.
This function takes the MonoBoolean reuse parameter but does not use it. The DisconnectEx and TransmitFileEx are always invoked with the TF_REUSE_SOCKET flag which suggests that when reuse is false the socket will be reused anyway.
I noticed this problem when investigating a socket related issue which now looks like an application problem. So I do not know if the is genuinely a defect at this point, however the LOGDEBUG message in the function suggests that the reuse parameter is significant.