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.
We're seeing a very similar looking bug at present.
We're on stable and our stack trace looks like:
"at System.Net.WebConnection.BeginRead (System.Net.HttpWebRequest request, System.Byte buffer, Int32 offset, Int32 size, System.AsyncCallback cb, System.Object state) [0x0001d] in /Developer/MonoTouch/Source/mono/mcs/class/System/System.Net/WebConnection.cs:885 \n at System.Net.WebConnectionStream.BeginRead (System.Byte buffer, Int32 offset, Int32 size, System.AsyncCallback cb, System.Object state) [0x001ab] in /Developer/MonoTouch/Source/mono/mcs/class/System/System.Net/WebConnectionStream.cs:392 \n at System.Net.WebConnectionStream.Read (System.Byte buffer, Int32 offset, Int32 size) [0x00007] in /Developer/MonoTouch/Source/mono/mcs/class/System/System.Net/WebConnectionStream.cs:332 \n at System.IO.StreamReader.ReadBuffer () [0x00012] in /Developer/MonoTouch/Source/mono/mcs/class/corlib/System.IO/StreamReader.cs:376 \n at System.IO.StreamReader.Read (System.Char buffer, Int32 index, Int32 count) [0x00077] in /Developer/MonoTouch/Source/mono/mcs/class/corlib/System.IO/StreamReader.cs:453 \n at System.IO.StreamReader.ReadToEnd () [0x00040] in /Developer/MonoTouch/Source/mono/mcs/class/corlib/System.IO/StreamReader.cs:557 \n at:"
Our problem is intermittent.
Is it likely we're hitting a similar bug? Is there any more info about this issue?
We've looked more at our problem here.
It seems to be related to chunked data coming back from our webserver.
If we return 20 records (approx 3500 bytes) then this is just one Http chunk and we receive the response fine.
If we return 30 records (approx 5000 bytes) then this is split into two chunks and we then see an ObjectDisposedException while trying to read all the stream within our client.
We've tried also on a wpf client and that same code works fine for 100s of records with or without the chunking.
For now we have a workaround for our problem - we just need to request much smaller chunks of data - but it would be nice to know if this the same Xam.iOS issue as this bug report - or whether this is a new bug. Also, if you've got any other suggestions please let us know.
This bug should be fixed already.
Martin, which revision will contain this fix?
*** Bug 12355 has been marked as a duplicate of this bug. ***