Search Issue Tracker
Duplicate
Votes
0
Found in
2021.3.25f1
2022.2.18f1
2023.1.0b15
2023.2.0a13
Issue ID
UUM-35442
Regression
No
Player crashes on Android when using "-systemallocator" command in terminal
Reproduction steps:
1. Open the attached Project “BugRepro”
2. Make sure “Assets/Scenes/SampleScene” is added to the “Scenes in Build” list in Build Settings
3. Build and Run on an Android device (ARM64 IL2CPP was used)
4. Once the Player has loaded up, exit the app
5. Run the “systemallocator” command in terminal
6. Observe the Player
Expected result: Application doesn’t crash
Actual result: Application crashes when two observable images are about to load
Reproducible with: 2021.3.25f1, 2022.2.18f1, 2023.1.0b15, 2023.2.0a13
Couldn’t test with: 2020.3.48f1 (Player doesn’t load)
Reproducible on:
Pixel 6
Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Notes: Development mode in Build Settings must be toggled off when Building the Project to reproduce the issue. Reproduces on OpenGLES3, but not Vulkan
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This should be fixed in the following Unity versions:
* 2021.3.28f1
* 2022.3.5f1
* 2023.1.3f1
* 2023.2.0a22
Duplicate of another internal issue: UUM-40105: Android application crashes with system allocator ARM64, Android 11 or higher, MemoryManager::GetAllocatorContainingPtr