Forum Xamarin.Android
We are excited to announce that the Xamarin Forums are moving to the new Microsoft Q&A experience. Q&A is the home for technical questions and answers at across all products at Microsoft now including Xamarin!

We encourage you to head over to Microsoft Q&A for .NET for posting new questions and get involved today.

android.os.DeadObjectException crash only on certain devices

Hello,

I am contacting you regarding a very bizarre crash we have encountered on our Xamarin Android application, but only on certain devices. On the same exact device except a different kernel version, we do not encounter this crash.
So far we have reproduced this crash on a sample app with SupportToolBar (support libs v 25.4.0.2), but if we remove the toolbar from our main application, we still reproduce the crash, so there must be another crash source.
Do you have suggestions on how to fix this crash or at least how to analyse it?

You will find below our investigations report:

Description:
The application crashes after a short period of time. It can happen while navigating through activities or just by interacting with a component.
Only a few devices have this problem.
No crash report is received in Hockey App.

Device with crash:
Model: Sonim Smart-Ex 01
Processor: Qualcomm MSM8926
Android Version: 4.4.4
Security Patch level: 2015-12-01
Kernel: 3.4.0-g87b8f32-00001-g37b31dd Fri Dec 11 17:57:27 IST 2015

Device without crash:
Model: Sonim Smart-Ex01
Processor: Qualcomm MSM8926
Android Version: 4.4.4
Security Patch Level: 2016-08-05
Kernel: 3.4.0-g87b8f32-00026-g65ceae3 Thu 9 Aug 17:59:11 IST 2016

LogCat window:
12-29 13:49:08.902 Sonimtech Smart-Ex 01 Info 1854 ActivityManager Process XXXX (pid 8019) has died.
12-29 13:54:22.942 Sonimtech Smart-Ex 01 Warning 1854 ActivityManager android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:660)
at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:769)
at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:2459)
at com.android.server.am.ActivityStack.finishTopRunningActivityLocked(ActivityStack.java:2336)
at com.android.server.am.ActivityStackSupervisor.finishTopRunningActivityLocked(ActivityStackSupervisor.java:2087)
at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:9852)
at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:9731)
at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:10400)
at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:9941)
at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)

VS Output window:
01-02 10:43:17.431 E/mono-rt ( 8120):
01-02 10:43:17.431 E/mono-rt ( 8120): No native Android stacktrace (see debuggerd output).
01-02 10:43:17.431 E/mono-rt ( 8120):
01-02 10:43:17.431 E/mono-rt ( 8120):
01-02 10:43:17.431 E/mono-rt ( 8120): =================================================================
01-02 10:43:17.431 E/mono-rt ( 8120): Got a SIGSEGV while executing native code. This usually indicates
01-02 10:43:17.431 E/mono-rt ( 8120): a fatal error in the mono runtime or one of the native libraries
01-02 10:43:17.431 E/mono-rt ( 8120): used by your application.
01-02 10:43:17.431 E/mono-rt ( 8120): =================================================================
01-02 10:43:17.431 E/mono-rt ( 8120):
01-02 10:43:17.431 F/libc ( 8120): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 8120 (tim.mynotif.dev)

Already checked:
- Device Settings, Other installed applications : Same on both devices
- Activity attributes : Still crashing
- Wifi/4G Network: Still crashing
- Realm Database, create new Application using Realm: No crash
- Support Libraries, create new Application using Support Libs: Crash with SupportToolBar (If we remove the Toolbar from the Main Application, it's still crashing)

Posts

  • andnesandnes USMember ✭✭✭

    Were you able to solve this?

  • GuillaumeDavoGuillaumeDavo FRUniversity

    No, there is an issue opened on xamarin-android/issues/1791

  • ModalCitizanModalCitizan Member

    Hello, ladies/gentlemen.

    I am getting this with extensive play of my newly ported game. This is a serious blocker. I won't release my game with it bombing after long periods of play. Has anyone had a chance to run this issue down? There is limited information in various corners of the internet, but nothing too useful. Please help.

Sign In or Register to comment.