Bug 281 - armeabi architecture needs to be tied to a single core.
Summary: armeabi architecture needs to be tied to a single core.
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 1.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-08-12 09:57 UTC by Jonathan Pryor
Modified: 2012-08-30 15:47 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Jonathan Pryor 2011-08-12 09:57:32 UTC
Attempting to run a multi-threaded app on a multi-core processor with the armeabi architecture (ARMv5) results in crashes; see:


To Reproduce:

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.
Comment 1 Jonathan Pobst 2011-11-07 10:32:49 UTC
Public archive link:

Comment 2 Jonathan Pryor 2011-11-08 09:11:04 UTC
Fixed in 020991ad.
Comment 3 Gerardo 2012-08-30 15:47:57 UTC
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!