1.5.2 跳转loadScene 部分机型(华为)闪退

loading场景 使用 cc.loader.loadRes 一张一张加载纹理合集之后 再 cc.director.loadScene(‘Lobby’); 的时候 出现闪退 … 公司 其它机型正常没问题 IOS 基本没问题 但是 就一部 华为 基本是必定闪退 以下是
Android studio 的闪退信息~

求大手子 来分析一下~
闪退 前的信息
08-31 16:36:48.310 17501-17524/? D/cocos2d-x debug info: Create unpacker 071d04cd2 for e16de294-e4e1-42b0-9993-b0f5b2f5b7b6
08-31 16:36:48.316 17501-17524/? D/cocos2d-x debug info: Create unpacker 0cec73028 for b66da403-b122-4e1e-b12e-da4a5e144137
08-31 16:36:48.361 17501-17524/? D/cocos2d-x debug info: Create unpacker 09305f682 for 86939c07-85fb-4c61-94d5-947ba088bf24
08-31 16:36:48.563 17501-17524/? D/cocos2d-x debug info: Create unpacker 0d9b0d9de for ecca2a60-27de-462b-a08d-3c4e05e2d22f
08-31 16:36:48.711 17501-17524/? D/cocos2d-x debug info: Create unpacker 0d2b5f5b2 for 3e4213e3-fc8a-48b2-add1-5f5c0915bea3
08-31 16:36:48.763 17501-17524/? D/cocos2d-x debug info: Create unpacker 0d5895191 for 4e767924-a5b7-4aa5-8587-3e9ae6b5217f
08-31 16:36:48.778 17501-17524/? D/cocos2d-x debug info: Create unpacker 09ecb7f50 for 4344f9ab-0899-4c6a-979e-86d59a984252
08-31 16:36:48.931 17501-17524/? D/cocos2d-x debug info: Create unpacker 0a874386a for b9b56229-6764-4bcd-b7bf-a46fede89e4e
08-31 16:36:49.128 17501-17524/? D/cocos2d-x debug info: Create unpacker 0834c176e for f42e3099-a8df-4a00-ad63-f3c09c7a1ba1
08-31 16:36:49.356 17501-17524/? D/cocos2d-x: basic_object_finalize 0x72394342e0 …
08-31 16:36:49.357 17501-17524/? D/cocos2d-x: jsbindings: finalizing JS object 0x7238edffd0 (WebSocket)
08-31 16:36:49.357 17501-17524/? D/cocos2d-x: jsbindings: finalizing JS object 0x7235701220 (WebSocket)

errer
[ 08-31 16:49:11.365 408: 408 W/ ]
debuggerd: handling request: pid=21933 uid=10382 gid=10382 tid=21958
08-31 16:49:11.493 22036-22036/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-31 16:49:11.493 22036-22036/? A/DEBUG: Build fingerprint: ‘HUAWEI/WAS-AL00/HWWAS-H:7.0/HUAWEIWAS-AL00/C00B180:user/release-keys’
08-31 16:49:11.493 22036-22036/? A/DEBUG: Revision: ‘0’
08-31 16:49:11.493 22036-22036/? A/DEBUG: ABI: ‘arm64’
08-31 16:49:11.493 22036-22036/? A/DEBUG: pid: 21933, tid: 21958, name: GLThread 25270 >>> com.yaoyao.hongzhongmj <<<
08-31 16:49:11.493 22036-22036/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
08-31 16:49:11.493 22036-22036/? A/DEBUG: x0 0000000023ffffff x1 0000000000000000 x2 0000000000ffffff x3 0000000000000000
08-31 16:49:11.493 22036-22036/? A/DEBUG: x4 0000000000000004 x5 0000000000000004 x6 000000723bbeb080 x7 0000000000000000
08-31 16:49:11.493 22036-22036/? A/DEBUG: x8 00000000000000a5 x9 0000000008817554 x10 0000000059a7cd87 x11 0000000000058eb9
08-31 16:49:11.493 22036-22036/? A/DEBUG: x12 0000000000000016 x13 00000000fa000000 x14 0000000000000000 x15 00056d60b18fa630
08-31 16:49:11.493 22036-22036/? A/DEBUG: x16 000000723eb72840 x17 0000007260820340 x18 0000007254ef3b30 x19 0000000000000001
08-31 16:49:11.493 22036-22036/? A/DEBUG: x20 000000723b72b1c0 x21 0000000000000001 x22 0000007254b14c00 x23 0000000000000001
08-31 16:49:11.493 22036-22036/? A/DEBUG: x24 0000007254ef4ca0 x25 000000723b130900 x26 0000007254ef4c98 x27 000000723b12cf38
08-31 16:49:11.493 22036-22036/? A/DEBUG: x28 0000007235056190 x29 0000007254ef7488 x30 000000723dd39630
08-31 16:49:11.493 22036-22036/? A/DEBUG: sp 0000007254ef4bd0 pc 000000723dd392a8 pstate 0000000060000000
08-31 16:49:11.503 22036-22036/? A/DEBUG: backtrace:
08-31 16:49:11.504 22036-22036/? A/DEBUG: #00 pc 00000000006962a8 /data/app/com.yaoyao.hongzhongmj-1/lib/arm64/libcocos2djs.so
08-31 16:49:11.504 22036-22036/? A/DEBUG: #01 pc 000000000069662c /data/app/com.yaoyao.hongzhongmj-1/lib/arm64/libcocos2djs.so
08-31 16:49:11.824 32464-21312/? E/MtpServerEx: SendStorageInfoChanged 00010001
08-31 16:49:12.256 1201-6444/? E/HsmCoreServiceImpl: onTransact in code is: 102
08-31 16:49:12.269 1201-24160/? E/ProcessInfoCollector: getProcessInfo: failed to find this proc

可能跟架构有关系,从 log 看用的是 arm64 的库,你可以构建 armv7 或者 armeabi 的库试试

首先谢谢panda回复 我们构建的时候 把armv7 跟 arm64-v8a 都勾选了 API level 是19

看看你的设备 API Level 是多少。可以尝试在构建选项里面去掉 arm64 看看还会不会崩溃

api level 是19

重新看了一下 log,感觉跟 websocket 有关系,应该是在 1.6 中修复了

好的~ 那我先升1.6打包看一下.