Android上的ETC纹理pkm文件访问问题,引起崩溃

android上有些etc纹理的pkm文件出现Unable to access asset data: -1的问题,貌似在一些老一点的机型上才出现。把这个文件放到sd卡上读取又正常。

日志
07-13 21:59:43.727 E/szipinf (21935): Error reading asset data

07-13 21:59:43.727 E/szipinf (21935): Unable to access asset data: -1

07-13 21:59:43.752 E/szipinf (21935): Error reading asset data

07-13 21:59:43.752 E/szipinf (21935): Unable to access asset data: -1

07-13 21:59:43.752 F/libc (21935): Fatal signal 11 (SIGSEGV) at 0x00000018 (code=1), thread 21980 (Thread-489)

07-13 21:59:43.857 I/DEBUG (12347): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

07-13 21:59:43.857 I/DEBUG (12347): Build fingerprint: ‘samsung/m0zs/m0:4.1.2/JZO54K/I9300ZSEMC1:user/release-keys’

07-13 21:59:43.862 I/DEBUG (12347): pid: 21935, tid: 21980, name: Thread-489 >>> com.xxx <<<

07-13 21:59:43.862 I/DEBUG (12347): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000018

07-13 21:59:44.232 I/DEBUG (12347): r0 00000018 r1 00000000 r2 5e209810 r3 000000cd

07-13 21:59:44.232 I/DEBUG (12347): r4 00000000 r5 67aaf298 r6 000002a4 r7 67aaf298

07-13 21:59:44.232 I/DEBUG (12347): r8 613111c0 r9 631ef848 sl 631ef8e8 fp 631ef858

07-13 21:59:44.232 I/DEBUG (12347): ip 5e24090c sp 5e542b20 lr 5dcba26d pc 5dcba26e cpsr 00000030

07-13 21:59:44.232 I/DEBUG (12347): d0 3fe0000000000000 d1 0004cccccccccccc

07-13 21:59:44.232 I/DEBUG (12347): d2 0004cccccccccccc d3 000fffffffffffff

07-13 21:59:44.232 I/DEBUG (12347): d4 3cf4000000000000 d5 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): d6 0000000000000000 d7 000003613f800000

07-13 21:59:44.232 I/DEBUG (12347): d8 416fca0540000000 d9 416fca0555555555

07-13 21:59:44.232 I/DEBUG (12347): d10 0000000000000000 d11 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): d12 0000000000000000 d13 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): d14 0000000000000000 d15 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): d16 0000ffff02000000 d17 4010000000000000

07-13 21:59:44.232 I/DEBUG (12347): d18 0014cccccccccccd d19 3fe0000000000000

07-13 21:59:44.232 I/DEBUG (12347): d20 3fe16bcc41e90000 d21 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): d22 0000000000000000 d23 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): d24 0000000000000000 d25 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): d26 0000000000000000 d27 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): d28 0000000000000000 d29 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): d30 0000000000000000 d31 0000000000000000

07-13 21:59:44.232 I/DEBUG (12347): scr 80000010

07-13 21:59:44.232 I/DEBUG (12347):

07-13 21:59:44.232 I/DEBUG (12347): backtrace:

07-13 21:59:44.237 I/DEBUG (12347): #00 pc 0040c26e /data/data/com.xxx/lib/libcocos2dcpp.so (cocos2d::Sprite::setSpriteFrame(cocos2d::SpriteFrame*)+41)

07-13 21:59:44.237 I/DEBUG (12347): #01 pc 0040c269 /data/data/com.xxx/lib/libcocos2dcpp.so (cocos2d::Sprite::setSpriteFrame(cocos2d::SpriteFrame*)+36)

07-13 21:59:44.237 I/DEBUG (12347):

我们的项目也出现一样的问题
小改下报错的ETC贴图能临时过去 但下次改后再打包又有可能出现
cocos2dx3.3

也遇到这个问题了,又解决办法吗?

顶下 也遇到同样问题