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.
Attached is a crash log from an app that is randomly crashing for unknown reasons.
This bug report is to start tracking the issue and ask/collect for information that might help investigate the issue.
**Build Date & Platform:**
=== Xamarin Studio ===
Version 5.9.7 (build 9)
Installation UUID: a1a11d65-6b26-4444-a7b8-7f95e2136866
Mono 4.0.4 ((detached/cb6d6b2)
GTK+ 2.24.23 (Raleigh theme)
Package version: 400040002
=== Apple Developer Tools ===
Xcode 7.0.1 (8228)
=== Xamarin.iOS ===
Version: 220.127.116.11 (Business Edition)
Build date: 2015-09-16 17:04:13-0400
=== Xamarin.Android ===
=== Xamarin Android Player ===
=== Xamarin.Mac ===
=== Build Information ===
Release ID: 509070009
Git revision: 31fa64709030b3edb971237780a452a4c69943c4
Build date: 2015-09-17 11:44:37-04
Xamarin addins: b105d33d8cd72911ff2cf3ee0b7715d37e5f19a6
=== Operating System ===
Mac OS X 10.10.5
Rodrigo had taken a look at the crash log originally.
By any chance have you guys seen this crash and have a clue on what triggers it?
My guess is that this is some sort of memory corruption in the ObjC class data.
Some way to reproduce the crash would likely be required to figure out what's going on (with memory corruption it's very unlikely we'll be able to track it down with crash reports, since the crash usually occurs a long time after the memory was corrupted).
@John it's not something we have seen before. We'll need a way to duplicate the issue (even if it's not easy to reproduce).
@Joseph, that stack trace isn't fully symbolicated (several frames with "No matching symbols found:undefined"). Are crash reports symbolicated properly if you get them from Xcode's Organizer instead? Or can you try with a debug build and see if that's properly symbolicated?
I'd try to get to the bottom of this issue first (it's easier to diagnose than a random memory corruption, it's a good lead as anything else, and Objective-C exceptions can theoretically corrupt memory as well).
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!