Unity Issue Tracker - [Mobile] Player freezes on "UnityClassic::Baselib_SystemFutex

Fixed

Fixed in 2022.3.19f1, 2023.2.8f1, 2023.3.0b5, 7000.0.0a1

Votes

116

Found in

2022.3.19f1

2023.2.7f1

2023.3.0b5

7000.0.0a1

Issue ID

UUM-41806

Regression

Yes

[Mobile] Player freezes on "UnityClassic::Baselib_SystemFutex_Wait" or silently crashes

Jul 05, 2023

How to reproduce:
1. Open the "IN_45267" project
2. In the Build Settings "Run Device" dropdown select the desired device
3. Press Build And Run
4. Force stop the Player after 5-10 minutes and run it again (repeat a couple of times)

Expected result: Player doesn't crash or freeze
Actual result: Player crashes or freezes

Reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a22

Testing environment: Windows 10 Pro

Reproducible on these devices (crash):
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880
VLNQA00489, Htc 10 (HTC 10), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00363, Samsung Galaxy Z Fold2 5G (SM-F916B), Android 11, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650 (only when using Vulcan Graphics API)
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS

Reproducible on these devices (freeze):
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: NOT FOUND, GPU: Mali-G76
Samsung S20 5G (user reported)

Not reproducible on this device:
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540

Stack Trace from user:
UnityClassic::Baselib_SystemFutex_Wait(int*, int, unsigned int)
ujob_wait_for(ujob_control_t*, ujob_handle_t, int)
CompleteFenceInternal(JobFence&, WorkStealMode)
CullScene(CullResults&)
Camera::CustomCull(CameraCullingParameters const&, CullResults&, bool)
RenderManager::RenderOffscreenCameras()
PlayerRender(bool)

Notes:
- I'm able to reproduce freeze only with 2023.1.3f1 and 2023.2.0a22 with Samsung Galaxy S10+
- Not reproducible on Windows Standalone and WebGL

Resolution Note:

This issue appears to have been a duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-41806, which is fixed as of 2022.3.19f1
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-41806

Comments (17)

HkingAuditore

Jan 17, 2024 06:18

Not fixed on Unity 2022.3.16f1
jakob-leitner

Dec 20, 2023 21:31

We run into this issue on Samsung Galaxy S20 using Unity 2022.3.15f1.
rmiha

Dec 07, 2023 10:50

We're still reproducing that freeze in 2023.1.20f1, however it's better than before. So I guess the fi helped but didn't fully resolve the issue.
actopolus

Nov 13, 2023 04:06

Hi, QA team. When it will be fixed and released?
It is top contributor to ANRs and Crashes on Android.
RandomUnityDev123

Nov 07, 2023 18:42

I do see a spike in "CompleteFenceInternal" crashes in our 2022.3.10f1 clients but only for Android. Does anyone have an iOS crash stack I can use to look for clues in our crash reports?
BugiGames

Nov 03, 2023 18:03

Btw in 2021.3.25f1 I didn't find this bug, so decision was to downgrade there and wait...
BugiGames

Nov 03, 2023 15:36

On Unity 2022.3.12f same bug with mobile Galaxy A21s - game freezes after 10-20 min of gameplay, with android logcat its dosent show any error!
rmiha

Oct 23, 2023 13:12

I'm attaching similar crash:

0x234499: ujob_execute_job(ujob_control_t*, ujob_lane_t*, ujob_job_t*, ujob_handle_t, int) at ??:0:0

0x234399: ujob_wait_for(ujob_control_t*, ujob_handle_t, int) at ??:0:0

0x230d85: CompleteFenceInternal(JobFence&, WorkStealMode) at ??:0:0

0x5a3dfc: MeshRenderer::FinalizeUpdate(MeshBoundsJobData*, JobFence&) at ??:0:0

0x20210f: RendererUpdateManager::UpdateAll(RendererScene&) at ??:0:0

0x550060: RenderManager::UpdateAllRenderers() at ??:0:0

0x550a48: Camera::CustomRender(CullResults&, ShaderPassContext&, CameraRenderingParams const*, Camera::RenderFlag, Camera::PerformRenderFunction*, void (*)(), void (*)()) at ??:0:0

0x565a0c: RenderManager::RenderCameras(int, void (*)(), void (*)()) at ??:0:0

0x2424e9: PlayerRender(bool) at ??:0:0

0x23d4e1: ExecutePlayerLoop(NativePlayerLoopSystem*) at ??:0:0

0x23d503: ExecutePlayerLoop(NativePlayerLoopSystem*) at ??:0:0

0x23d6e3: PlayerLoop() at ??:0:0

0x346dbb: UnityPlayerLoop() at ??:0:0

0x356c57: nativeRender(_JNIEnv*, _jobject*) at ??:0:0

0x3052739: ?? at ??:0:0
rmiha

Oct 23, 2023 13:07

Correction: we can also see the same crash in crash reports from the builds made with 2022.2.2, but we were unable to reproduce internally so it looks like it's much harder to reproduce this with 2022.2.2.
rmiha

Oct 23, 2023 10:59

I was not able to reproduce this on 2022.2.2, but I reproduce it quite fast on 2022.2.3.

It's a lot harder to reproduce the problem if I disable multithreaded rendering.