Unity crashes (signal 11) - how to diagnose or fix

We are using an automated crash reporting service, and we're seeing a very high number of crashes which do not occur inside our code.

Here are a few examples:

Here's the device breakdown:
samsung GT-N7100 27%
samsung GT-I9060I 24%
samsung SM-T116NU 11%
samsung SM-G7102 9%
samsung GT-I9301I 9%
samsung SM-G360H 9%
samsung SGH-M919 8%
samsung SM-T560 8%

And OS breakdown:
4.4.2 58%
4.4.4 42%
4.4.3 1%
4.4 1%
5.0.1 1%
4.4.2_Eyal.H_Cell 1%

We have other reports of similar issues (they are classified as different crashes because the stack trace is slightly different), but overall, the top of the stack is similar for all (Unity library):

The game was released with Unity 5.3.6, our next release will use 5.3.6p8.

1. Is this a known Unity bug? we have no repro scenario so we cannot send a project, etc.
2. This occurs on the scale of hundreds of thousands of times (around 150k crashes in the past month).
3. Is there any way we can convert the addresses from the stack trace into actual useful information ? (function names) ?

Any help will be appreciated !! CC: @Yury-Habets

 

BUMP

 

Not to be a jerk and tell you to RTFM, but I have found that page from the manual. It didn't really help me, objdump didn't give me anything that makes sense, but it might help you.

https://docs.unity3d.com/Manual/MobileCrashes.html

Best of luck, there is nothing I hate more than debugging on mobile

 

I already got a nicer stack trace by using tools from the NDK:

This is a known bug that is said to be worked on (not too comforting as its open for months now). Looks likeit is related to resource or scene loafing.

Here's a link to the currently open bug: https://issuetracker.unity3d.com/issues/android-unity-crashes-loading-a-scene

 

Yes you already mentioned that @superpig is on top of it. waiting for more info... this is really killing us (over 100k crashes so far).

 

1% user affected due to this crash after updating Unity to 5.5.