Search Issue Tracker
Fixed in 2022.1.X
Votes
3
Found in
2021.1
2021.1.18f1
Issue ID
1362153
Regression
No
[Android] Specific project crash on pthread_mutex_lock when building with ARMv7 and ARM64 Architectures
Reproduction steps:
1. Open the user's attached project "Racing.zip"
2. Build And Run on Android
Expected result: Build works with no issues
Actual result: Build crashes
Reproducible with: 2021.1.20f1
Could not test with: 2019.4.30f1, 2020.3.18f1, 2021.2.0b12, 2022.1.0a9 (Due to errors when upgrading/downgrading the project) ("Exception: OBSOLETE")
First lines of the stracktrace:
08/26 00:51:12.939 16046 16071 Error AndroidRuntime #00 pc 00000000000687a8 /system/lib64/libc.so (pthread_mutex_lock) (BuildId: ff3fe0498c71765418437bcf4d102967)
08/26 00:51:12.939 16046 16071 Error AndroidRuntime #01 pc 000000000004584c /system/lib64/libc.so (dlmalloc+380) (BuildId: ff3fe0498c71765418437bcf4d102967)
08/26 00:51:12.939 16046 16071 Error AndroidRuntime #02 pc 0000000000047b5c /system/lib64/libc.so (dlcalloc+40) (BuildId: ff3fe0498c71765418437bcf4d102967)
08/26 00:51:12.939 16046 16071 Error AndroidRuntime #03 pc 0000000000019588 /system/lib64/libc.so (calloc+20) (BuildId: ff3fe0498c71765418437bcf4d102967)
08/26 00:51:12.939 16046 16071 Error AndroidRuntime #04 pc 000000000079c850 /data/app/com.beermoneygames.race-1/lib/arm64/libil2cpp.so (BuildId: f87d2a837ab3071e3c41e02b64ed5a8f39536711)
Reproducible with these devices:
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00002, Samsung S5 Neo LTE (SM-G903F), Android 6.0.1, CPU: Exynos 7 Octa 7580, GPU: Mali-T720
VLNQA00318, Oneplus 7Pro (GM1913), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00110, Samsung Galaxy Note2 (GT-N7100), Android 4.4.2, CPU: Exynos 4 Quad 4412, GPU: Mali-400 MP
N/A, Huawei - (ELS-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00264, Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00078, Motorola Nexus 6 (Nexus 6), Android 7.1.1, CPU: Snapdragon 805 APQ8084AB, GPU: Adreno (TM) 420
Not reproducible with these devices:
iPhone 8 Plus (iOS 14.4.2)
iPad 6th generation (iOS 14.4.2)
iPad Air 2 (iOS 11.0.3)
Notes:
-The issue reproduces with the "Development Build" setting turned on and off
-The issue happens when both ARMv7 and ARM64 are selected in the build settings, after removing the ARMv7 support, there were no issues
Comments (13)
-
rmgomez
Mar 29, 2022 18:50
We need this fix in Unity 2020.3
-
pandolfini
Nov 15, 2021 02:15
Same with Unity 2020.3.21. Can you confirm that this is updated in the latest Unity 2020.3.22?
-
RaventurnPatrick
Oct 07, 2021 12:45
Same with the latest Untiy 2019 LTS on the following Devices:
Samsung Galaxy S9+
OnePlus 9T
Nexus 5
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 2022.1):
This bug has been fixed by new build functionality that we introduced in 2021.2 and later. We have made changes to our approach to incremental builds that avoid the problem.