Bug 41239 - ServicePointManager is not getting cleaned up
Summary: ServicePointManager is not getting cleaned up
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-05-22 14:08 UTC by Alex Stefan
Modified: 2016-05-25 08:21 UTC (History)
2 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 41239 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 Alex Stefan 2016-05-22 14:08:09 UTC

I recently got into an issue on our Xamarin.Android apps.

     - ServicePointManager.DefaultConnectionLimit has default values = 2
     - For different reasons those 2 concurent connections get faulted and after this, every request to the server is getting timeout error, but it doesn't reach the server
     - When setting up the DefaultConnectionLimit to 200, the bug it doesn't seem to reproduce. Therefor I'm thinking that the faulted connections are not cleaned up when they should.

I took a look into the ServicePointManager.cs from the referencesource and it looks like the "IdleServicePointTimeoutCallback" is missing from the mono code, but it seems to be exactly what may fix the problem.
How should I fix this?

Thank you,