Demo中只有一个粒子，直接打包Android安装运行，一启动就闪退。没有任何有意义的报错，花了两天时间，从一个完整的大项目中排查出定位到是这一个粒子的问题。
打包设置如下：
我知道是这个mesh导致的闪退，但是3.4.2用的好好的，到3.6.1就莫名其妙的闪退。就算我换了这一个mesh，项目中还有2000个粒子。不知道还会不会有其他的闪退。只能先退回3.4.2了
DEMO:
361.zip (17.6 KB)
已测试机型：
Vivo x21A
小米 K40
三星 s21ultra
最后说一句：
从3.4.2升级到3.6.1的这两天着实难受，编辑器，浏览器各种警告给我刷屏，动不动刷几百条，我都忍了，想着只是警告而已，能利用上原生性能的提升，这一切都是值得的。但是最后直接来个闪退，哎
闪退的报错贴出来啊
2022-09-26 16:16:36.899 6361-21425/? E/memtrack: Couldn’t load memtrack module
2022-09-26 16:16:37.393 25546-25569/? A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 25569 (Thread-2), pid 25546 (game.sanguoidle)
2022-09-26 16:16:37.591 25607-25607/? A/DEBUG: Softversion: PD1728_A_7.10.32
2022-09-26 16:16:37.591 25607-25607/? A/DEBUG: Time: 2022-09-26 16:16:37
2022-09-26 16:16:37.591 25607-25607/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2022-09-26 16:16:37.591 25607-25607/? A/DEBUG: Build fingerprint: ‘vivo/PD1728/PD1728:9/PKQ1.180819.001/compiler07281740:user/release-keys’
2022-09-26 16:16:37.591 25607-25607/? A/DEBUG: Revision: ‘0’
2022-09-26 16:16:37.591 25607-25607/? A/DEBUG: ABI: ‘arm64’
2022-09-26 16:16:37.591 25607-25607/? A/DEBUG: pid: 25546, tid: 25569, name: Thread-2 >>> com.gz4358.sanguoidle <<<
2022-09-26 16:16:37.591 25607-25607/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: Cause: null pointer dereference
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: x0 0000000000000000 x1 000000000000000b x2 000000000000000b x3 0000000000000000
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: x4 00000000000000f4 x5 00000076b437ef64 x6 747865546e69616d x7 657275747865546e
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: x8 00000076b437f088 x9 00000076b437f05c x10 c261a109fed80d35 x11 9ddfea08eb382d69
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: x12 000cae4eae8f0caa x13 0000000000000065 x14 0000000000000010 x15 aaaaaaaaaaaaaaab
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: x16 00000076b5a2fa60 x17 00000076b598e9dc x18 0000000012c40370 x19 00000076b437f190
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: x20 00000076b248f940 x21 00000076b437f0b0 x22 00000076c9043430 x23 00000076b4380588
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: x24 00000076b4cf83ec x25 00000076b5a4c000 x26 000000750968ede9 x27 00000076b4380588
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: x28 000000750000a320 x29 00000076b437f0e0
2022-09-26 16:16:37.592 25607-25607/? A/DEBUG: sp 00000076b437f020 lr 00000076b4cf86b4 pc 00000076b4cf86d4
2022-09-26 16:16:37.593 25607-25607/? A/DEBUG: backtrace:
2022-09-26 16:16:37.593 25607-25607/? A/DEBUG: #00 pc 00000000009776d4 /data/app/com.gz4358.sanguoidle-FSnmWfSafc2PDSpy0v8y5A==/lib/arm64/libcocos.so
2022-09-26 16:16:37.593 25607-25607/? A/DEBUG: #01 pc 0000000000cc16f0 /data/app/com.gz4358.sanguoidle-FSnmWfSafc2PDSpy0v8y5A==/lib/arm64/libcocos.so
2022-09-26 16:16:37.593 25607-25607/? A/DEBUG: #02 pc 0000000000cc0d38 /data/app/com.gz4358.sanguoidle-FSnmWfSafc2PDSpy0v8y5A==/lib/arm64/libcocos.so
2022-09-26 16:16:37.593 25607-25607/? A/DEBUG: #03 pc 0000000000cc04c8 /data/app/com.gz4358.sanguoidle-FSnmWfSafc2PDSpy0v8y5A==/lib/arm64/libcocos.so
2022-09-26 16:16:37.593 25607-25607/? A/DEBUG: #04 pc 00000000015001c8 /data/app/com.gz4358.sanguoidle-FSnmWfSafc2PDSpy0v8y5A==/lib/arm64/libcocos.so
2022-09-26 16:16:37.902 1032-1032/? E//system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_09
2022-09-26 16:16:38.055 1784-2037/? E/InputDispatcher: channel ‘35ff603 com.gz4358.sanguoidle/com.cocos.game.AppActivity (server)’ ~ Channel is unrecoverably broken and will be disposed!
2022-09-26 16:16:38.099 1784-13481/? E/ActivityTrigger: activityResumeTrigger: not whiteListedcom.bbk.launcher2/com.bbk.launcher2.Launcher/90003028
2022-09-26 16:16:38.130 719-930/? E/: IProducerListener: malformed binder reply
2022-09-26 16:16:38.172 719-3997/? E/: IProducerListener: malformed binder reply
…已发
敢升级的都是勇士 帮你顶了一下
3.7才修复 那3.6 版本别人还可以用来生产吗？到了3.7可能又会有其他bug 那发3.6点几的意义何在
这个我确实改不了，对C艹不熟悉啊 
js引擎已经被魔改的不成样子了
