Bug 8435 - Random SIGABRT
Summary: Random SIGABRT
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 6.0.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-11-15 15:11 UTC by Pierce Boggan [MSFT]
Modified: 2012-11-16 14:16 UTC (History)
2 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 Pierce Boggan [MSFT] 2012-11-15 15:11:10 UTC
- The issue does not appear to occur on the simulator only on my iPhone.
- The particular code in question will sometimes executes successfully and sometimes fails. It usually fails after the app has been running for some time.
- The program uses two additional threads (aside from the UI thread). Only when these additional threads are running does there seem to be an issue.
- I have disabled any UI updating code and the crash still occurs. So the two additional threads are effectively running in complete isolation.
- The crash always seems to occur on the same non-UI thread.

Version Information:
Installation UUID: 85a4c5b0-317a-4c13-aaad-4619601fcd60
Mono 2.10.9 (tarball)
GTK 2.24.10
GTK# (
Package version: 210090011
Apple Developer Tools:
Xcode 4.5.1 (1842)
Build 4G1004
Monotouch: 6.0.4
Mono for Android: Not Installed

Build information:
Release ID: 30004007
Git revision: ea0108260c6a376ecaeffcdb7d03387bd51edda3
Build date: 2012-09-17 14:09:17+0000
Xamarin addins: ec43fd5cb223ead4234a9858d1b56eef03dad53a-dirty
Operating System:
Mac OS X 10.7.5
Darwin cpe-58-175-12-85.flin08.fli.bigpond.net.au 11.4.2 Darwin Kernel Version 11.4.2
Thu Aug 23 16:25:48 PDT 2012
root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64
Comment 3 Sebastien Pouliot 2012-11-15 15:26:25 UTC
Pierce, see my note on https://bugzilla.xamarin.com/show_bug.cgi?id=8407#c4

You'll find the same stack segment in comment #1 (and the same solution applies to fix it). However I cannot say if this will solve all issues.

When a test case is not possible (or hard to create) then we need the crash report (more complete than the stacktrace like above) and the device console logs (the later includes additional hints from iOS and, in this case, from the mono runtime requesting more trampolines of a certain type).
Comment 5 Sebastien Pouliot 2012-11-16 14:16:34 UTC