Sunday, 15 February 2015

crash - SIGSEGV and SIGBUS crashes with Xamarin.iOS Unified API -


We had a project on the classic API. Everything worked fine for 32 and 64-bit iOS devices.

Then we went to Integrated API . It starts crashing on some devices (mostly 64-bit devices), it crashes in many different locations and situations, these crashes are predictive and difficult to reproduce. But in the production version many users face these accidents.

We currently have the version of the app (let's call it version 1) which was created with the XMarin for iOS. IOS 8.6 (Stable Channel). SDK 8.1

We have lots of crash crashes with crash crashing (crash reporting service). All crashes are SIGSEGV (Reason: SEGV_MAPERR) , but may have different stack traces. It seems that some crashes occur only on 64-bit devices.

Then we created another version of the app to reproduce the issue (version 2). With its debug option turned on, the XMarin for iOS SDK 8.2 Made with iOS 8.8 (stable channel).

We now have similar crashes, most of them are on the background thread (not the main UI thread) and now all crashes are SIGBUS (Reason: BUS_ADRERR) .

What could be the root cause of such accidents? How to diagnose and fix it?

I had to face similarly after migrating to the Unified API

< P> It works fine with the classic API, but the accident started after upgrading.

So make sure that you are disposing objects on the UI thread or if you do not need to avoid dealing with it.

Hope it helps

This may be the reason that crashes occur on the background thread.

No comments:

Post a Comment