Search Issue Tracker
Fixed
Fixed in 2021.3.36f1, 2022.3.20f1, 2023.2.10f1, 2023.3.0b7, 2024.1.0a1
Votes
18
Found in
2021.3.28f1
2022.3.5f1
2023.1.5f1
2023.2.0b1
2023.3.0a3
Issue ID
UUM-44039
Regression
No
[Android] Application crash when methods are called in multiple threads
Reproduction steps:
1. Open the attached project “threadsProject”
2. Build the Project for Android
3. Run "adb logcat -s CRASH" in a Command Prompt or Terminal
4. Run the Application on the device
5. Observe the app's behaviour
Expected result: The app exits after running and doesn’t crash
Actual result: The app crashes on first the launch and displays the text “Crashed” on the second launch
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.5f1, 2023.2.0b1
Reproducible with these devices:
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00139 - Vivo Xplay6 (vivo Xplay6), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 7.1.1
VLNQA00132 - Xiaomi Mi 5s (MI 5s), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 6.0.1
Not reproducible with these devices:
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0
Tested with: Intel macOS 13.4.1
Notes:
- The application exits automatically when it finishes the work. If it crashes, it will show "Crashed" the next time the launch)
- It may need to run the application multiple times to reproduce the crash.
- The apps work properly when Mono is used instead of il2cpp
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
andersemil
Mar 07, 2024 08:08
So now 2021.3.36 is out but this is still a known issue according to the LTS releases web page, even though it says here that the fix is in review for that very release. Great procedure, Unity
Alan-Liu
Jan 16, 2024 09:35
There is a workaround to reduce the probability of the crash: https://forum.unity.com/threads/google-console-libil2cpp-so-sigbus-crash.1485249/#post-9544891
steven_unity84
Jan 15, 2024 14:53
We're going to be stuck on 2022 for a while. Will need a backport
ApoxolHR
Jan 15, 2024 12:37
This really needs to be back ported to at least 2022 as it is causing a lot of issues.
andersemil
Jan 08, 2024 15:38
Using mono as scripting backend is not possible, as Google Play Store only accepts ARM64 builds, and that requires IL2CPP. So we are stuck with an undiscoverable app until this issue is fixed
jhd
Dec 23, 2023 13:45
https://forum.unity.com/threads/google-console-libil2cpp-so-sigbus-crash.1485249/#post-9545092