3.5 安卓V8崩溃

Creator 3.x
#1

vivo给了1.5个G的日志，里面崩溃都是这几行，通过率太低了

image
image723×814 106 KB

--------- beginning of crash
05-31 16:32:16.989 27059 27094 F libc : Fatal signal 11 (SIGSEGV), code 2, fault addr 0x6f9254c0 in tid 27094 (Thread-2), pid 27059 ()
05-31 16:32:17.087 27375 27375 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-31 16:32:17.087 27375 27375 F DEBUG : Build fingerprint: ‘vivo/PD1809/PD1809:8.1.0/OPM1.171019.026/compil04252203:user/release-keys’
05-31 16:32:17.087 27375 27375 F DEBUG : Revision: ‘0’
05-31 16:32:17.087 27375 27375 F DEBUG : ABI: ‘arm64’
05-31 16:32:17.087 27375 27375 F DEBUG : pid: 27059, tid: 27094, name: Thread-2 >>> com.game.vivo <<<
05-31 16:32:17.087 27375 27375 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x6f9254c0
05-31 16:32:17.087 27375 27375 F DEBUG : x0 0000007fce230e30 x1 000000006f9254c0 x2 0000000000000001 x3 0000000000000000
05-31 16:32:17.087 27375 27375 F DEBUG : x4 0000007cf4f02588 x5 00000000173a3d30 x6 00000000173a3e10 x7 00000000001fffff
05-31 16:32:17.087 27375 27375 F DEBUG : x8 0000007d92dc6000 x9 0000000000000002 x10 0000000000000001 x11 0000000000000000
05-31 16:32:17.087 27375 27375 F DEBUG : x12 0000000000000000 x13 0000000000000000 x14 8e21dcf03aae491b x15 8e21dcf03aae491b
05-31 16:32:17.087 27375 27375 F DEBUG : x16 0000007d91b2e2a8 x17 0000007d91abcb3c x18 0000007cf4f02588 x19 0000000000000000
05-31 16:32:17.087 27375 27375 F DEBUG : x20 0000007d96896b80 x21 0000007d96896000 x22 0000000000001000 x23 0000007cf4cdbab0
05-31 16:32:17.087 27375 27375 F DEBUG : x24 0000007d91b36000 x25 0000007d91b36000 x26 0000007d91b36000 x27 0000007cf382eb88
05-31 16:32:17.087 27375 27375 F DEBUG : x28 000000000000007c x29 0000007cf4f01700 x30 0000007d91ad1494
05-31 16:32:17.087 27375 27375 F DEBUG : sp 0000007cf4f016a0 pc 000000006f9254c0 pstate 0000000080000000
05-31 16:32:17.093 27375 27375 F DEBUG :
05-31 16:32:17.093 27375 27375 F DEBUG : backtrace:
05-31 16:32:17.093 27375 27375 F DEBUG : #00 pc 00000000002ba4c0 /data/dalvik-cache/arm64/system@framework@boot-framework.art
05-31 16:32:17.093 27375 27375 F DEBUG : #01 pc 000000000008d490 /system/lib64/libc.so (__cxa_finalize+328)
05-31 16:32:17.093 27375 27375 F DEBUG : #02 pc 000000000001aa98 /system/lib64/libc.so (exit+24)
05-31 16:32:17.093 27375 27375 F DEBUG : #03 pc 000000000082e008 /data/app/com.game.vivo-JR4sGwbMNCd9b2ASNFbvMQ==/lib/arm64/libcocos.so (cc::Engine::close()+88)
05-31 16:32:17.093 27375 27375 F DEBUG : #04 pc 000000000085c8a8 /data/app/com.game.vivo-JR4sGwbMNCd9b2ASNFbvMQ==/lib/arm64/libcocos.so (JSB_closeWindowRegistry(v8::FunctionCallbackInfov8::Value const&)+152)
05-31 16:32:17.093 27375 27375 F DEBUG : #05 pc 000000000140f398 /data/app/com.game.vivo-JR4sGwbMNCd9b2ASNFbvMQ==/lib/arm64/libcocos.so (v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo)+548)
05-31 16:32:17.093 27375 27375 F DEBUG : #06 pc 000000000140e9f4 /data/app/com.game.vivo-JR4sGwbMNCd9b2ASNFbvMQ==/lib/arm64/libcocos.so
05-31 16:32:17.093 27375 27375 F DEBUG : #07 pc 000000000140e184 /data/app/com.game.vivo-JR4sGwbMNCd9b2ASNFbvMQ==/lib/arm64/libcocos.so
05-31 16:32:17.093 27375 27375 F DEBUG : #08 pc 00000000013230a8 /data/app/com.game.vivo-JR4sGwbMNCd9b2ASNFbvMQ==/lib/arm64/libcocos.so

#2

有没有人管呀~~

#3

ABI: ‘arm64’

你打包是不是没勾上64的？

#4

包含了arm64
刚才检查了一下，貌似是调用了game.end引起了崩溃？？
我都要退出游戏了，搞一个崩溃出来，顺利的让我过不了审？
先不调用game.end吧，验证一下是否过审。

#5

从调用栈上看，是 JS 的某个 callback 调用了 game.end()，在销毁整个游戏过程中导致的崩溃，检查下什么地方做的

#6

都是在按钮的回调里面做的，这是正常的做法吧？点击退出游戏，直接game.end()呀

#7

暂时先在java层写System.exit(0);绕过game.end()，目前没有发现崩溃，先应付一下审核吧

#8

正常应该游戏没有退出游戏的按钮 只能用户自己杀进程

#9

原生包，隐私政策弹窗，不同意的话就game.end()