5,380 questions
Debugging crash on Android
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 64%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EI%3C/text%3E%3C/svg%3E)
ioberry
1
Reputation point
Basically I have a Xamarin.Native app on Android. The problem is that it crashes randomly with the following stacktrace:
A/libc: Fatal signal 11 (SIGSEGV), code -6 (SI_TKILL) in tid 10892 (Thread Pool Wor), pid 10704
A/DEBUG: * * * * * * * * * * * * * * * *
A/DEBUG: Build fingerprint: 'google/redfin/redfin:11/RQ1A.201205.010/6953398:user/release-keys'
A/DEBUG: Revision: '0'
A/DEBUG: ABI: 'arm'
A/DEBUG: Timestamp: 2021-02-01 19:13:03+0700
A/DEBUG: pid: 10704, tid: 10892, name: Thread Pool Wor >>> com.ioberry.myapp <<<
A/DEBUG: uid: 10685
A/DEBUG: signal 11 (SIGSEGV), code -6 (SI_TKILL), fault addr --------
A/DEBUG: r0 00000000 r1 b1eaa304 r2 ae799610 r3 00000000
A/DEBUG: r4 b81baba0 r5 b81aab20 r6 c4810520 r7 c48104e8
A/DEBUG: r8 b8966310 r9 ee950260 r10 00000000 r11 b1eaa2d0
A/DEBUG: ip 00000000 sp b1eaa2d0 lr c56d8f9c pc eed6c70c
A/DEBUG: backtrace:
A/DEBUG: #00 pc 0000070c <anonymous:eed6c000>
A/DEBUG: #01 pc 002cff98 /data/app/com.ioberry.myapp-fbsz6pYxUiTSFosV752aUw==/lib/arm/libmonosgen-2.0.so (mono_thread_info_get_small_id+16)
There is not much of information that could point to the exact origin of this problem, but we can assume the following:
- Something happens in one of the threads from the pool (execution of an asynchronous task ??), which leads to the whole process being killed (ST_KILL)
- StackOverflow says it might be related to INotifyPropertyChanged (we use it in our project along with Reactive Extensions)
So, how to debug and investigate crashes like this? Unfortunately debuggers in Android Studio or Visual Studio do not detect anything at all.
What tools can help here?
Is there a way to record thread calls (C#/managed code) in order to find source of this crash?
Developer technologies .NET Xamarin
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 87%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
JarvanZhang 23,971 Reputation points2021-02-04T13:49:02.003+00:00 Hi, ioberry-9258. This issue is usually related to the memory release, multiple releases result in abnormal exit.Did you execute the release operations in your project? And what's the version of VS you test? Try to update the VS to the lastest stable version and try again.
-
ioberry 1 Reputation point
2021-02-05T08:55:06.217+00:00 Hi. Well, we don't use native code on our side. Except for the fact that we are using a third party library (includes native .so binaries) for displaying the maps, which I believe is the source of the problem. Removing its initialization code seems to have stopped the app from crashing.
-
JarvanZhang 23,971 Reputation points
2021-02-05T08:58:12.72+00:00 Thanks for sharing the info. You could report the problem to the author of the library for a solution.
-
ioberry 1 Reputation point
2021-02-09T16:05:19.56+00:00 Unfortunately this can be a bit problematic as they do not support Xamarin (library is distributed for native applications as AAR) and you have to make bindings yourself. I didn’t find any information on this issue in their repository (which makes me think that no one has encountered this problem in native apps because our app dies stably in less than 2 minutes) and I didn’t have time to investigate the exact reason of this behaviour :(
But I guess I need to spend a little time investigating it.
Sign in to comment
Sign in to answer