Home » Android » android – Pre-launch report "Issue: native crash"

android – Pre-launch report "Issue: native crash"

Posted by: admin May 14, 2020 Leave a comment

Questions:

Google Play Console Pre-launch report states a crash with my app running on Pixel Android 8.0 (no issues with the others). When watching the replay, I see no issue and don’t see the app crash.

This is the info provided.

Issue: Native crash of com.xxxxxxxxx


Build fingerprint:
‘google/sailfish/sailfish:8.0.0/OPR3.170623.008/4294783:user/release-keys’
Revision: ‘0’
ABI: ‘arm64’
pid: 10010, tid: 10046, name: ControllerMesse >>> com.xxxxxxx <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr ——–
Abort message: ‘Cannot get a dirty matrix!’
x0 0000000000000000 x1 000000000000273e x2 0000000000000006 x3 0000000000000008
x4 feff71647164636d x5 feff71647164636d x6 feff71647164636d x7 7f7f7f7f7f7f7f7f
x8 0000000000000083 x9 09ee441dd405312c x10 0000000000000000 x11 0000000000000001
x12 ffffffffffffffff x13 ffffffffffffffff x14 ffffffffff000000 x15 ffffffffffffffff
x16 0000007e7b1662f8 x17 0000007e7b1085d0 x18 00000000ebad6082 x19 000000000000271a
x20 000000000000273e x21 000000007099a7f0 x22 0000000012c6d508 x23 0000000012fffd20
x24 00000000135a0278 x25 0000000000000000 x26 0000000000000000 x27 0000000012ffffb8
x28 00000000706b05b0 x29 0000007e5f2ee1f0 x30 0000007e7b0bc994
sp 0000007e5f2ee1b0 pc 0000007e7b1085d8 pstate 0000000060000000

Can anyone point me in the right direction.

How to&Answers:

Android is open source, so when debugging something like this I always start with Google. A Google search for ‘android source “cannot get a dirty matrix”‘ leads here.

https://android.googlesource.com/platform/frameworks/base/+/master/libs/hwui/RenderProperties.h

Now this doesn’t tell you how to fix it, but does tell you it is something wrong with the native rendering code with a device running Android O, using 64 bit native code.

If it was my app I’d try to find another Android Oreo device with an arm64 processor and see if it happens to me. But it is going to be hard to debug, and just as likely to be a bug with the OS or your game engine than something you can fix yourself (unless you have been writing native rendering code).