Search Issue Tracker
Duplicate
Votes
0
Found in
2020.3.48f1
2021.3.25f1
2022.2.19f1
2023.1.0b16
2023.2.0a14
Issue ID
UUM-35491
Regression
No
[Quest 2] Player crashes on Quest 2 with MemoryManager::VirtualAllocator::GetBlockInfoFromPointer
Steps to reproduce:
1. Open the attached user's project "Repro TextureArray Memory Bug Quest.zip" for Quest 2 or "Repro TextureArray Memory Bug.zip" for non-Oculus Quest devices
2. Make sure that IL2CPP is selected as the Scripting Backend
3. Make sure that Release Build is selected as the C++ Compiler Configuration
4. Build the APK and install it to Quest 2 or non Oculus Quest devices but do not launch the application
5. Open CMD/Terminal and run the application with the following command:
adb shell am start -n com.DefaultCompany.ReproTextureArrayMemoryBug/com.unity3d.player.UnityPlayerActivity -e 'unity' '-systemallocator'
6. Observe the crash once the application launches
Expected results: The player does not crash
Actual Results: The player crashes on Quest 2 with MemoryManager::VirtualAllocator::GetBlockInfoFromPointer
Reproducible in: 2020.3.48f1, 2021.3.25f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a14
Reproducible on these devices:
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 12
Not reproducible on these devices:
N/A, Samsung Galaxy S6 edge+ (SM-G928F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
N/A, Xiaomi Mi Note2 (Mi Note 2), Android 8.0.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
N/A, Xiaomi - (Redmi Note 8 Pro), Android 9, CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4
N/A, Samsung - (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Environment tested on:
Windows 10
Notes:
-As noted by the Customer if the 26'th line of TextureArray.cs is commented out, the application no longer crashes
-Does not reproduce with Mono Backend
-Stacktrace symbolized using AndroidLogcat stack trace utility tool and is attached named (“ReleaseBuildLogcatStacktrace.txt”)
-SystemAllocator must be used since it was recommended to the Customer and DebugAllocator is not the solution
-
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
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
- "Rendering Debugger" displays incorrect overdraw count when using "Unlit/Texture" shader
- Scene and Game views break when the Editor window is snapped with the Microsoft PowerToys
- Materials do not transfer texture when the "Shader" parameter is changed from "Unlit/Texture" to "Universal Render Pipeline/Unlit"
- [Linux][Vulkan] Crash when opening searchable dialog
- The "Shader error in 'AE/Leaves': "Undefined punctual shadow filter algorithm"" error appears when build completes on a specific project
This is a duplicate of issue #UUM-35442