Bug 43727 - KeyNotFoundException raised deep inside Socket.Close
Summary: KeyNotFoundException raised deep inside Socket.Close
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: master
Hardware: Other Linux
: --- normal
Target Milestone: Untriaged
Assignee: marcos.henrich
Depends on: 43172
  Show dependency tree
Reported: 2016-08-24 22:21 UTC by Andi McClure
Modified: 2016-08-25 07:47 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 43727 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 original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Andi McClure 2016-08-24 22:21:18 UTC
For at least the last week, and apparently on *ARM64 only*, our automated test MonoTests.Remoting.RemotingServicesTest.MarshalThrowException will periodically fail with a managed exception deep inside the guts of Socket.Close. The exception appears to be unrelated to the MarshalThrowException test as such and occurs because the test calls ChannelServices.UnregisterChannel() during cleanup.

Examples (with full stacktraces):


Expected behavior: If something goes wrong during Socket.Close(), a useful error message should occur and not a KeyNotFoundException.
Comment 1 Alexander Köplinger [MSFT] 2016-08-24 23:02:28 UTC
This is related to #43172 (or maybe a dupe). The error will only occur when MONO_TESTS_IN_PROGRESS is set like we do in CI, the KeyNotFoundException comes from this array access: https://github.com/mono/mono/blob/dfbd2bcf829d1bc62451aa824dc6a1aba68370bb/mcs/class/System/System.Net.Sockets/SafeSocketHandle.cs#L63