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
GitHub or Developer Community 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.
If you run concurrent requests using the Mono HttpClientHandler, the network stack will JAM or throw numerous weird internal exceptions. Mono 3.4 doesn't show this, but mono 3.6+ does show this. Regular .NET does not have this issue either.
I originally discovered this on Android when I was trying to reduce GREF usage by switching from ModernHttpClient based off of OkHttp back to the mono Http stack. I found that my application could not run successfully. None the less, this applies across all mono platforms (ios/android/linux/etc)
I have created a test case that illustrates the issue.
You have to run the node js script inside so that the test case has a server to talk to. When you run the test case, a working version of mono will complete (printing start/stop 10 times). When you use a broken version of mono, it will hang completely, usually with no stops printed at all.
A working run should look like this
>lucite:mono-http-hang tj$ mono mono-http-hang/bin/Debug/mono-http-hang.exe
Fixed in master
Until this fix is released, does anyone know of a workaround for now?
It didn't make it to mono 3.10
Does anyone know when this will be solved?
This is affecting me to in Xam.Android 184.108.40.206. Any news on when the fix will be released?
We are also having the same problem. Any update?
The workaround I found for now is to create a new HttpClient for each request and then dispose of it when you're done.
Is there an update on this? I am running the latest stable Xamaron.Android 220.127.116.11 and cannot make concurrent requests on Android and iOS seems fine.
You need Xamarin.Android 5.0 which is the first version with the fix
*** Bug 26044 has been marked as a duplicate of this bug. ***