My game crashed while playing

Hello,
I just compiled and tried to play my game and got the crash after 30 seconds.
Unfortunately, this happens once, so can’t find any repro steps, however, I have the crash logs.

I’m using Unity 2022.2.4.

NB: I’ve turned on Graphics Jobs (Experimental), not sure it is related, but as i can’t repeat this crash, i can’t say it because of this feature for sure.

Native StackTrace:

We did not turn on Graphics Jobs (Experimental). We are using URP, and many users are reporting the same crash. But we can’t find a solution. If you find a solution, please share.

Same issue here, updated to 2022.2.5f1 because of the Thread crashes in previous releases, but now we got this instead. We do not have many graphics, so that is not the issue. We are using some async awaits and plugin DOTween. Maybe others use these same things ?

Hi there! Updated to 2022.2.5 as well and got even more crashes in iOS.
I’m using asyncs awaits as well, but the android build works fine w/o any crashes.
I’m able to play for around 10 minutes till the end of the level on my iPhone 14 pro max, however, iPhone 8 randomly crashes max during the first 13 seconds of play.
Hope this week’s release will fix this.

Here we have many android crashes (especially latest android versions) in the previous version of unity (2022.1.21).
Did the update to 2022.2.5 yesterday and first thing this morning were 2 crashes with this new description.
I did not update the iOS to 2022.2.5 yet, because the very known FBSdk compile issues with Xcode, but maybe I’m glad I did not to that yet, iOS seems ok with 2022.1.21 for now.
I’m thinking it might be the async calls, so now changing the scripts to the Unity way (Enumerator).
Hopefully this will solve the issue, but it is not happening very often so it is hard to reproduce for me.

We reverted back to 2020.3 version of unity (and target android sdk 33) and crashes are gone.
For us the problem was probably caused by the Vulkan graphics setting which is enabled by default on 2022 version.
We stick to 2020 version for now.

Can confirm, our crash rate went up 3x after changing from 2022.1 to 2022.2… we’re back on 2022.1.24 to avoid the crash-fest.

Just did a small test on my device and it still crushed on 2022.2.15 - I’ve just left my device running for like 30-50 min with the game opened and it crashed with that exact error message

Is there a chance to get anybody from Unity on it? My project crashes after certain amount of time without me touching the screen.

You can find a stack trace coming from 2022.2.15 below:

null pointer dereference: SIGSEGV  0x0000000000000000
#00 pc 0x5739b8 libunity.so (dynamic_array<ActiveReflectionProbe, 0ul>::~dynamic_array()) (BuildId: 803bec3be648cadd)
#01 pc 0xaf5e98 libunity.so (GfxDevice::ExecuteAsync(int, void (*)(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*), GfxDeviceAsyncCommand::ArgScratch**, GfxDeviceAsyncCommand::Arg const*, JobFence const&)) (BuildId: 803bec3be648cadd)
#02 pc 0x12c29dc libunity.so (__unw_getcontext) (BuildId: 803bec3be648cadd)
#03 pc 0x16fc1a libunity.so (BuildId: 803bec3be648cadd)
#04 pc 0x1483b6 libunity.so (BuildId: 803bec3be648cadd)
#05 pc 0xa78588 libunity.so (RenderNodeQueue::Reset(bool)) (BuildId: 803bec3be648cadd)
#06 pc 0x25498f4 libil2cpp.so (BuildId: f71145acfc328cf5)
#07 pc 0xa7831c libunity.so (RenderNodeQueue::~RenderNodeQueue()) (BuildId: 803bec3be648cadd)
#08 pc 0x12c29dc libunity.so (__unw_getcontext) (BuildId: 803bec3be648cadd)
#09 pc 0x16fc1a libunity.so (BuildId: 803bec3be648cadd)
#10 pc 0xa78334 libunity.so (RenderNodeQueue::~RenderNodeQueue()) (BuildId: 803bec3be648cadd)
#11 pc 0x56e71c libunity.so (ScriptableRenderContext::ExecuteScriptableRenderLoop()) (BuildId: 803bec3be648cadd)
#12 pc 0x12c29dc libunity.so (__unw_getcontext) (BuildId: 803bec3be648cadd)
#13 pc 0x16079c libunity.so (BuildId: 803bec3be648cadd)
#14 pc 0x16079c libunity.so (BuildId: 803bec3be648cadd)
1 Like

same here with 2022.2.x; no exact repo, just a random crash in the dynamic_array destructor. Unity, anyone?

Have anybody tried the 2022.2.17 yet? I run a build yesterday for 7h+ and it haven’t crashed, so it looks promising.

Yes report the bug to unity and attach your project. As you describe the bug is reproducable, so I would expect it to be fixed.