Unity3d 'Fatal signal 11 (SIGSEGV), code 1'

项目一切都是OK的,接入某渠道SDK后,打开app 就 crash。人啊,这一辈子注定要遇到几个 ‘SIGSEGV’,摊手。

01-05 18:48:12.124: A/libc(727): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 776 (UnityMain)
01-05 18:48:12.124: E/libEGL(727): call to OpenGL ES API with no current context (logged once per thread)
01-05 18:48:12.234: A/DEBUG(533): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-05 18:48:12.234: A/DEBUG(533): Build fingerprint: 'samsung/c5pltezc/c5pltechn:6.0.1/MMB29M/C5000ZCU1APJ4:user/release-keys'
01-05 18:48:12.234: A/DEBUG(533): Revision: '10'
01-05 18:48:12.234: A/DEBUG(533): ABI: 'arm'
01-05 18:48:12.234: A/DEBUG(533): pid: 727, tid: 776, name: UnityMain  >>> com.kongzhong.c1.uc <<<
01-05 18:48:12.234: A/DEBUG(533): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
01-05 18:48:12.254: A/DEBUG(533):     r0 9ebc82a8  r1 00000008  r2 00000000  r3 00000000
01-05 18:48:12.254: A/DEBUG(533):     r4 a169ec36  r5 9ebc7010  r6 9eaadb10  r7 fffff0d4
01-05 18:48:12.254: A/DEBUG(533):     r8 00001298  r9 0000002b  sl 00000001  fp 00000002
01-05 18:48:12.254: A/DEBUG(533):     ip 0000002b  sp a082e378  lr ffffffff  pc a0d01c3c  cpsr 60070010
01-05 18:48:12.254: A/DEBUG(533): backtrace:
01-05 18:48:12.254: A/DEBUG(533):     #00 pc 004d2c3c  /data/app/com.kongzhong.c1.uc-1/lib/arm/libunity.so
01-05 18:48:12.254: A/DEBUG(533):     #01 pc 00333cb4  /data/app/com.kongzhong.c1.uc-1/lib/arm/libunity.so
01-05 18:48:12.254: A/DEBUG(533):     #02 pc 0030e0d8  /data/app/com.kongzhong.c1.uc-1/lib/arm/libunity.so
01-05 18:48:12.254: A/DEBUG(533):     #03 pc 0035e680  /data/app/com.kongzhong.c1.uc-1/lib/arm/libunity.so
01-05 18:48:12.254: A/DEBUG(533):     #04 pc 00509e58  /data/app/com.kongzhong.c1.uc-1/lib/arm/libunity.so
01-05 18:48:12.254: A/DEBUG(533):     #05 pc 0050cc00  /data/app/com.kongzhong.c1.uc-1/lib/arm/libunity.so
01-05 18:48:12.254: A/DEBUG(533):     #06 pc 003f3441  /data/app/com.kongzhong.c1.uc-1/oat/arm/base.odex (offset 0x21f000)

毫无头绪,看backtarce,挂在unity的C++代码里,鬼知道是什么,当然可以用ndk-stack tool来看具体的堆栈信息,如何使用 参考链接,但并没有任何有价值的信息。

SIGSEGV之前有可能还会遇到说GL找不到上下文的报错。

call to OpenGL ES API with no current context (logged once per thread)

一开始以为Unity开了Multithreaded Rendering,导致crash。 关掉了之后,确实不crash了,但是屏幕全粉了,心想要么材质掉了,要么shader跪了,开始报下面错:

-------- GLSL link failed, no info log provided.

一番google之后,在Unity 坛子里名叫haruki_tachihara的网友(貌似霓虹国友人)解决了我的问题,很简单
it was resolved by loading the game scene after the empty scene.
竟然添加一个空场景中转一下就好了,而且多线程打开也没问题了,就这样所有问题都好了,也不crash了。现在想想大概是渠道sdk在splash界面就初始化, 把UnityMain进程挂起导致的。 现在国内渠道为了让接入的游戏打开就先显示自己的logo,也是操碎了心。

–EOF–

王在京同学 /
Published under (CC) BY-NC-SA in categories Unity3d  tagged with Unity3d