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.
Created attachment 1124 [details]
Test app that reproduces the error
This issue is similar to the resolved bug 1534. When the bug manifests, the observed behavior is the same as bug 1534 (mysterious stack trace with no exception and an app freeze and ANR message).
I have created a test case that will consistently reproduce the error. It seems that a mixture of heavy network, file IO, memory, and UI updating causes it to trigger. Running the attached test case for about 60 seconds will reproduce the error. It creates 2 threads that download and write a large file to disk (endlessly), and 3 threads that use a lot of memory then make https requests (endlessly), all the while the UI is being updated (via Handler.Post()).
Not sure if this has anything to do with the GC as the assertion I experience with bug 1534 is not present.
Fixed on trunk. Will be released after 4.0.2