Search Issue Tracker
Fixed
Fixed in 2022.3.5f1
Votes
0
Found in
2022.3.4f1
Issue ID
UUM-49200
Regression
Yes
[Android] Crash "MemoryManager::VirtualAllocator::GetBlockInfoFromPointer(void const*)" when the project is built with Development Build and opening the Player
How to reproduce:
1. Open the "IN_53346" project
2. In the Build Settings "Run Device" dropdown, select the desired device
3. Press Build And Run
Expected result: Player doesn't crash
Actual result: Player crashes
Reproducible with: 2022.3.4f1
Not reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a4
Fixed in: 2022.3.5f1
Reproducible on: Windows 10 Pro
Not reproducible on: No other environment tested
Reproducible on these devices:
Xiaomi Xiaomi 11T (21081111RG), Android 13, CPU: NOT FOUND, GPU: Mali-G77 MC9
VLNQA00517, Oneplus OnePlus 10 Pro 5G (NE2213), Android 12, CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno (TM) 730
Not reproducible on these devices:
VLNQA00512, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: Exynos 9 (9820), GPU: Mali-G76
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
VLNQA00431, Xiaomi Mi 11 (M2011K2G), Android 11, CPU: Snapdragon 888 SM8350, GPU: Adreno (TM) 660
Notes:
- Regressed version not found as testing and checking would take unreasonably too long
- Not reproducible with Windows Standalone Platform
- Couldn’t test on iOS due to an error “Framework not found FBLPromises” popping up during the building of the app
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Add comment