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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
System.InvalidOperationException: Operation is not valid due to the current state of the object
at System.Net.ServicePoint.RemoveConnectionGroup (System.Net.WebConnectionGroup group) [0x00000] in <filename unknown>:0 (code.cs:1)
at System.Net.ServicePoint.CheckAvailableForRecycling (System.DateTime& outIdleSince) [0x00000] in <filename unknown>:0 (code.cs:1)
at System.Net.ServicePoint.IdleTimerCallback (System.Object obj) [0x00000] in <filename unknown>:0 (code.cs:1)
at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00000] in <filename unknown>:0 (code.cs:1)
Please provide a test case that demonstrates the issue so we can fix it.
i believe my company pays enough to Xamarin (>50 enterprise licenses), so we can focus on writing our app, and not reproducing your bugs.
It is obvious that your code is buggy, look at stracktrace. It is a race in your code. And it is fucking difficult to repro. Ask your developers to repro it. Should be easy for guy who introduced that bug.
As you just said, if this is a race condition that is very hard to reproduce, there's not much magic we can do with just this backtrace. Sorry to say that.
What can be done, that would help get this fixed, is if there's some chunk of code and some testing instructions that would get us to reproduce the issue.
We'll take a look at the code in question but anything else you can share on the setup that triggers it would help us.
https://github.com/mono/mono/commit/a769e74c5320f2cfa85efe80f2e1c1d8470c271b - seems it was fixed.
Sad to see that you can't even handle your process properly and discover what is fixed