Android (Quest) Crashing/Freezing 64bit IL2CPP

Hi, we are encountering two issues, that happen anywhere from very very often (for some users), to not at all for others (same devices and OSs)

One which has been happening a bunch, the logs look like

05-25 19:36:37.181     0     0 W kgsl_iommu_fault_handler: 18265 callbacks suppressed

05-25 19:36:37.181     0     0 F kgsl-3d0: |kgsl_iommu_fault_handler| GPU PAGE FAULT: addr = CF7CE1E00 pid= 21857 name=even.forfunlabs

05-25 19:36:37.181     0     0 F kgsl-3d0: |kgsl_iommu_fault_handler| context=gfx3d_user TTBR0=0x490001173b8000 CIDR=0x5561 (read translation fault)

05-25 19:36:37.181     0     0 E kgsl-3d0: ---- nearby memory ----

05-25 19:36:37.181     0     0 E kgsl-3d0: [00000007FFFFC000 - 0000000800000000]   (pid = 21857) (command)

05-25 19:36:37.181     0     0 E kgsl-3d0: <- fault @ CF7CE1E00

05-25 19:36:37.181     0     0 E kgsl-3d0: *EMPTY*

followed by a bunch of

fence timeout on [0000000000000000] after 100ms

(attached a log file)

This error seems to result in 2 types of visual anomalies. Or maybe more accurately, this error occurs in the logs when 2 visual anomalies occur:
1. the view freezes between 2-3 frames, and shakes wildly between them.
2. a lot of the scene (opaque solid flicker hard, often completely vanishing), while random black squares appear in the view. More can be found here: https://forums.oculusvr.com/develop...squares-or-pixels-covering-most-of-the-screen

I'm not sure if this is anything Unity itself can do, but maybe someoe can help.



-----------

The second issue is a null pointer dereference. One happens on pc, that with the help of a unity support dev (i assume dev), was able to look at the stack, which lead to some unity cpp code where unity is trying to lock/release a lock on a null object.

I'm seeing a dereference crash in android, and wondering if it's the same cause...but I don't know how to read it.

This loooooks like it's pointing to something in unity code, but I don't know how to use this.
I appears my symbols.zip wasn't being generated for the last few builds... so i'll enable it and use the
instructions here
https://support.unity3d.com/hc/en-u...23.1506680629.1590970183-883981991.1563403398

java.lang.Error: FATAL EXCEPTION [main]

Unity version     : 2019.3.4f1

Device model      : Oculus Quest

Device fingerprint: oculus/vr_monterey/monterey:7.1.1/NGI77B/655140.17060.0:user/release-keys

Caused by: java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

Version '2019.3.4f1 (4f139db2fdbd)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'

Build fingerprint: 'oculus/vr_monterey/monterey:7.1.1/NGI77B/655140.17060.0:user/release-keys'

Revision: '0'

ABI: 'arm64'

Timestamp: 2020-05-31 20:45:57-0400

pid: 22969, tid: 23010, name: Thread-3  >>> quest.eleven.forfunlabs <<<

uid: 10058

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0

Cause: null pointer dereference

    x0  0000000000000000  x1  0000000000000000  x2  0000000000000180  x3  0000000000000004

    x4  0000000000000000  x5  0000000000000040  x6  000000000000003f  x7  0000000000000000

    x8  0000000000000000  x9  0000000000000004  x10 0000000000001190  x11 000000000000015a

    x12 0000000000000005  x13 00000000000040a1  x14 0000000000000025  x15 0000007fa6ba3810

    x16 0000007f8baf01e0  x17 0000007fa6adaf40  x18 0000000000000024  x19 0000007f84ef46c0

    x20 0000000000000a49  x21 0000000000000002  x22 00000000000001c0  x23 0000000000000000

    x24 0000000000008f37  x25 0000007f8b7d2110  x26 0000007f8bb72000  x27 0000007f84ef46c0

    x28 0000007f83a7c108  x29 0000007f803ff370

    sp  0000007f803fefb0  lr  0000007f8ae053b0  pc  0000007fa6adb0a8

backtrace:

      #00 pc 000000000001b0a8  /system/lib64/libc.so (memset+360) (BuildId: 0d82b5085cc8358649be6ff5d14ed691)

      #01 pc 00000000004233ac  /data/app/quest.eleven.forfunlabs-1/lib/arm64/libunity.so (BuildId: 0247c6c5cb8a15dc3ebc20d5fe4869b6453a5f59)

      #02 pc 0000000000909c58  /data/app/quest.eleven.forfunlabs-1/lib/arm64/libunity.so (BuildId: 0247c6c5cb8a15dc3ebc20d5fe4869b6453a5f59)

      #03 pc 00000000004175e4  /data/app/quest.eleven.forfunlabs-1/lib/arm64/libunity.so (BuildId: 0247c6c5cb8a15dc3ebc20d5fe4869b6453a5f59)

      #04 pc 0000000000411050  /data/app/quest.eleven.forfunlabs-1/lib/arm64/libunity.so (BuildId: 0247c6c5cb8a15dc3ebc20d5fe4869b6453a5f59)

      #05 pc 000000000057b7b8  /data/app/quest.eleven.forfunlabs-1/lib/arm64/libunity.so (BuildId: 0247c6c5cb8a15dc3ebc20d5fe4869b6453a5f59)

      #06 pc 00000000008b7e58  /data/app/quest.eleven.forfunlabs-1/lib/arm64/libunity.so (BuildId: 0247c6c5cb8a15dc3ebc20d5fe4869b6453a5f59)

      #07 pc 00000000008b9b88  /data/app/quest.eleven.forfunlabs-1/lib/arm64/libunity.so (BuildId: 0247c6c5cb8a15dc3ebc20d5fe4869b6453a5f59)

      #08 pc 00000000008b1040  /data/app/quest.eleven.forfunlabs-1/lib/arm64/libunity.so (BuildId: 0247c6c5cb8a15dc3ebc20d5fe4869b6453a5f59)

      #09 pc 0000000000314478  /data/app/quest.eleven.forfunlabs-1/lib/arm64/libunity.so (BuildId: 0247c6c5cb8a15dc3ebc20d5fe4869b6453a5f59)

      #10 pc 0000000000076454  /system/lib64/libc.so (__pthread_start(void*)+204) (BuildId: 0d82b5085cc8358649be6ff5d14ed691)

      #11 pc 000000000001e204  /system/lib64/libc.so (__start_thread+16) (BuildId: 0d82b5085cc8358649be6ff5d14ed691)

    at libc.memset(memset:360)

    at libunity.0x4233ac(Native Method)

    at libunity.0x909c58(Native Method)

    at libunity.0x4175e4(Native Method)

    at libunity.0x411050(Native Method)

    at libunity.0x57b7b8(Native Method)

    at libunity.0x8b7e58(Native Method)

    at libunity.0x8b9b88(Native Method)

    at libunity.0x8b1040(Native Method)

    at libunity.0x314478(Native Method)

    at libc.__pthread_start(void*)(__pthread_start:204)

    at libc.__start_thread(__start_thread:16)

 

I'm seeing the same `null pointer dereference` crash on my IL2CPP Quest builds. Did you ever find anything about this?

 

I'm getting it too, did you find any solution to it?