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 6737 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
Wanted: actual test case.
Socket.Close(int) allows a "timeout" value to be provided:
The problem is that the timeout isn't actually used, because we never linger. Following the code, the client calls Socket.Close(int):
Socket.Close(int) sets linger_timeout, then calls Dispose():
Which calls Dispose(bool):
Dispose(bool) sets connected=false (line 1196), then calls Linger(IntPtr):
The first thing Linger() does?
if (!connected || linger_timeout <= 0)
Dispose(bool) just set connected=false, therefore !connected is true, therefore we immediately return without lingering at all.
This is obviously broken. I'm not immediately sure how to fix it, and I don't want to fix it until we have a proper test case for this scenario.