Pre-launch report "Issue: native crash"

时间:2018-06-19 11:12:59

标签: android crash android-emulator prelaunch

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.

2 个答案:

答案 0 :(得分:1)

Android是开源的,因此在调试此类内容时,我总是从Google开始。 Google搜索“ android源代码“无法获取脏矩阵” ”的结果在这里出现。

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

现在,这并没有告诉您如何解决它,但确实告诉您,使用64位本机代码运行Android O的设备的本机渲染代码有问题。

如果这是我的应用程序,我将尝试查找另一台具有arm64处理器的Android Oreo设备,看看是否发生在我身上。但这将很难调试,并且可能是操作系统或游戏引擎的错误,而不是您可以自行修复的错误(除非您一直在编写本机渲染代码)。

答案 1 :(得分:0)

我也偶然发现了这个(可能是出于不同的原因)。我将以下库降级到以下版本后,错误从报告中消失了:

com.google.firebase:firebase-perf:19.0.7 (downgrade from 19.0.8)
com.google.firebase:firebase-firestore-ktx:21.4.3 (downgrade from 21.50.0)
com.google.firebase:firebase-config-ktx:19.1.4 (downgrade from 19.2.0)

无法确切指出问题所在,但我猜firebase-perf应该归咎于此。