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.
Attempting to run a multi-threaded app on a multi-core processor with the armeabi architecture (ARMv5) results in crashes; see:
Take the project attached to Bug #245, comment out the GC.Collect() call on line 39 (as described in Bug #245 Comment 2), and deploy a Release build to a Xoom (or other multi-CPU device), it crashes ~instantly.
We should fix the armeabi runtime so that it's tied to a single core.
Public archive link:
Fixed in 020991ad.
Hello - please have a look at Bug #6654. I think that the armeabi, multi-core fix sitll has something to be adjusted, as some internal objects of the framework are being disposed when they shouldn't. As mentioned, compiling to armeabi-v7a seems to remove the problem. Thank you!