Forum Discussion
saikiran_n
2 years agoProtege
Unity app on Quest2 crashing immediately after launching (After the Splash Screen)
Hello everyone, we recently updated our project to Unity 2022.3 LTS and v56 Oculus SDK. And we are facing this issue. Sometimes upon launch of game, scenes load and game works fine and sometimes it crashes right immediately after splash screen.
Have been encountering this issue on Quest2 store builds.
Attached is the crash report and stack trace.
Can someone provide insights on how to address/fix this issue?
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: Version '2022.3.5f1 (9674261d40ee)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: Build fingerprint: 'oculus/hollywood/hollywood:12/SQ3A.220605.009.A1/50600670051800150:user/release-keys'
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: Revision: '0'
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: ABI: 'arm64'
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: Timestamp: 2023-09-01 12:59:45.896768319+0530
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: pid: 24566, tid: 24622, name: Thread-3 >>> com.Company.Product <<<
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: uid: 10048
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr --------
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: Cause: null pointer dereference
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: x0 0000000000000000 x1 0000000000000000 x2 0000000000000010 x3 0000000000009146
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: x4 0000000000000010 x5 000000000000003b x6 00000072b61d6350 x7 7f7f7f7f7f7f7f7f
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: x8 0000000000000006 x9 0000000000000000 x10 0000000000001cf1 x11 0000000000000073
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: x12 0000000000000502 x13 00000073c4bd69cc x14 b400007350a2d6f0 x15 0000000000000000
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: x16 0000007375030550 x17 000000747f7400f0 x18 00000072b575e000 x19 0000007331e7cf90
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: x20 0000000000000000 x21 0000000000000002 x22 0000000000000010 x23 0000000000000000
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: x24 0000000000008f37 x25 0000007373e6757c x26 00000073750eb000 x27 0000007331e7cf90
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: x28 00000073402e2fd0 x29 00000072e08d5da8
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: lr 00000073748e6558 sp 00000072b61d73f0 pc 000000747f740144 pst 0000000060001000
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: backtrace:
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: #00 pc 0000000000085144 /apex/com.android.runtime/lib64/bionic/libc.so (memset+84) (BuildId: 0fdc1142906507383ea46be55881c2e4)
2023-09-01 12:59:45.896 24566-24622/? E/CRASH: #01 pc 0000000000c0f554 /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
2023-09-01 12:59:45.897 24566-24622/? E/CRASH: #02 pc 0000000000bea74c /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
2023-09-01 12:59:45.897 24566-24622/? E/CRASH: #03 pc 0000000000bffebc /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
2023-09-01 12:59:45.897 24566-24622/? E/CRASH: #04 pc 0000000000dbf634 /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
2023-09-01 12:59:45.897 24566-24622/? E/CRASH: #05 pc 0000000000db81ac /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
2023-09-01 12:59:45.897 24566-24622/? E/CRASH: #06 pc 0000000000db7ef4 /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
2023-09-01 12:59:45.897 24566-24622/? E/CRASH: #07 pc 0000000000679160 /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
2023-09-01 12:59:45.897 24566-24622/? E/CRASH: #08 pc 00000000000dddec /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+132) (BuildId: 0fdc1142906507383ea46be55881c2e4)
2023-09-01 12:59:45.897 24566-24622/? E/CRASH: #09 pc 000000000008a02c /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 0fdc1142906507383ea46be55881c2e4)
********** Crash dump: **********
Build fingerprint: 'oculus/hollywood/hollywood:12/SQ3A.220605.009.A1/50600670051800150:user/release-keys'
#00 0x0000000000085144 /apex/com.android.runtime/lib64/bionic/libc.so (memset+84) (BuildId: 0fdc1142906507383ea46be55881c2e4)
#01 0x0000000000c0f554 /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
ApiGLES::ClearBufferSubData(unsigned int, gl::BufferTarget, long, long)
??:0:0
#02 0x0000000000bea74c /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
BufferManagerGLES::AcquireBuffer(unsigned long, DataBufferGLES::BufferUsage, GfxBuffer*, bool)
??:0:0
#03 0x0000000000bffebc /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
GfxDeviceGLES::UpdateComputeConstantBuffers(unsigned int, ConstantBufferHandle*, unsigned int, unsigned long, unsigned char const*, unsigned int const*, unsigned int const*, int const*)
??:0:0
#04 0x0000000000dbf634 /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
GfxDeviceWorker::RunCommand(ThreadedStreamBuffer&)
??:0:0
#05 0x0000000000db81ac /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
GfxDeviceWorker::RunExt(ThreadedStreamBuffer&)
??:0:0
#06 0x0000000000db7ef4 /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
GfxDeviceWorker::RunGfxDeviceWorker(void*)
??:0:0
#07 0x0000000000679160 /data/app/~~BOLQ4aAGR0w-UZNS-k6a8A==/com.Company.Product-PRgYMmhJkSsgnj0X0ghTGg==/lib/arm64/libunity.so (BuildId: 33cf275551b4fb92)
Thread::RunThreadWrapper(void*)
??:0:0
#08 0x00000000000dddec /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+132) (BuildId: 0fdc1142906507383ea46be55881c2e4)
#09 0x000000000008a02c /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 0fdc1142906507383ea46be55881c2e4)7 Replies
Replies have been turned off for this discussion
- josvdwestExplorer
Same problem for us. Any updates?
- saikiran_nProtege
josvdwest For us, there was a canvas with Render Mode set to Screen Space - Overlay in the launch/initial scene, which was added for testing purpose during development.
Removing that has solved the issue for us.
How did we get to know it?
- We were looking after all the errors and warnings being logged when launching the game. We have been addressing one by one and checking the builds. That is when we have found a warning related to "Screen Space Overlay canvas being used in VR - Was that intentional ... etc" - AyfelExpert Protege
We are getting the same crash but no canvas in overlay at all in our scene so we are pretty stuck. We are using OpenGL + Unity 2022.3, if I switch to Vulkan there are no crashes, but due to requirements we cannot switch
- kennard-consultingExpert Protege
Any update on this? I'm facing the same (horrible) issue
- josvdwestExplorer
For our app, Remio, this happened because we were trying to use a custom splash screen with a free tier of Unity. When we upgraded our Unity plan, we stopped having this error.
- kennard-consultingExpert Protege
At least anecdotally, this appears to be related to Canvas.
For you, it was a custom splash screen (presumably a Canvas with 'Screen Space - Overlay' render mode). For another post, it was they had an unused Canvas with 'Screen Space - Overlay' lying around. For me, I was using a old implementation of a UI. I rewrote it to use FlatUnityCanvas as shipped with the SDK.
Crashes seem to have stopped (so far)...
- MichatkiHonored Guest
For me it started to happen when I enabled "Baked Global Illumination". No matter what settings for it I use, it crashes with this exception. Only RealTime Ligthting works, so I stick with it for now.
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 1 year ago
- 1 year ago
- 1 year ago