OK, thanks for the clarification. That freeze happens during a session of HttpWebRequests. The "stacktrace:" message shown sometimes indicates that the crash is within WebAsyncResult.AB but more usually it's within the processing (eg. decompression) of the response. So I wondered whether a stream-related glitch might be causing it, but clearly it's not.
NB. Prior to 1.2.0 I did see general long pauses throughout the app, these have now gone. The issue recorded in this new bug (1.2.0 and 1.9.0) is not a pause - the app just stops and doesn't continue (and doesn't die either.) The only "smoking gun" is the mysterious "stacktrace:" message which is being generated for some reason (by Mono?) but which doesn't result in an application exception or termination. Andy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Pryor Sent: 30 September 2011 14:55 To: Discussions related to Mono for Android Subject: Re: [mono-android] Trouble with Android.Graphics On Sep 30, 2011, at 4:58 AM, Andrew Sinclair wrote: > Given that this is a general stream-related issue, could it be causing the > random issues I've seen around HttpWebRequests? > (http://bugzilla.xamarin.com/show_bug.cgi?id=1031) It's not stream-related, it's wrapped-java-stream related. HttpWebRequest doesn't involve Java streams at all, just mono's normal Stream-atop-libc support, and thus should act normally. I'm not sure what bug 1031 has to do with HttpWebRequest, though; I don't see HttpWebRequest mentioned, and it's about long GC pauses... - Jon _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
