https://bugzilla.novell.com/show_bug.cgi?id=675362
https://bugzilla.novell.com/show_bug.cgi?id=675362#c1 --- Comment #1 from Chris Howie <[email protected]> 2011-02-26 01:38:55 UTC --- The number of reads (or perhaps the computation time to construct the objects) does seem related, as the block goes away entirely if I either wrap the WebConnectionStream in a BufferedStream, or read the contents of the WebConnectionStream in 4096-byte chunks, write those to a MemoryStream, and then perform the deserialization using the MemoryStream. Right now I am using the BufferedStream approach as a temporary workaround, so this bug is not blocking me. But it does strike me as odd, and I would definitely be interested to know what's going wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
