Android Fatal signal 11 (SIGSEGV) at 0x636f7d89 (code=1). How can it be tracked down?

Question

I\'ve been reading the other posts on tracking down the reasons for getting a SIGSEGV in an Android app. I plan to scour my app for possible NullPointers relate

Answer 1

In my case (I am using Xamarin Forms) this error was thrown due to a binding error - e.g. :

<Label Grid.Column="4" Grid.Row="1" VerticalTextAlignment="Start" HorizontalTextAlignment="Center"  VerticalOptions="Start" HorizontalOptions="Start" FontSize="10" TextColor="Pink" Text="{Binding }"></Label>

Basically I deleted the view model property by mistake. For Xamarin developers, if you have the same issue, check your bindings...

Answer 2

If you had added some native C code in your project this answer could be helpful.

I had added some native C code in android project.

Now i was trying to access that code which was returning native string to me, before processing the the string i had set its default value as nullptr. Now upon retrieving its value in java code ran into this issue.

As our native C code is out from java directory so getting no clue of exact line of code which is creating the issue. So i would suggest you to check your .cpp file and try to find any clue there.

Hope so you will get rid of the issue soon. :)

Answer 3

I had the issue when I was creating a PDF using Android's PDF APIs and I accidentally used the canvas.save() and canvas.restore() after I had closed a pdf page.

Answer 4

For me, on Android Studio 4.1, what did the trick was good ole File > Invalidate Cache & Restart

No more Fatal Signals after that. I'm sure it had something to do with the profiler, but can't be certain. I just know restarting AS stopped the crashes on my emulator.

Answer 5

I was getting this error by saving an object to the shared preferences as a gson converted string. The gson String was no good, so retrieving and deserializing the object was not actually working correctly. This meant any subsequent accesses to the object resulted in this error. Scary :)

Answer 6

If you are using vitamio library and this fatal error occur.

Then make sure that in your project gradle targetSdkVersion must be less than 23.

thanks.