Search Issue Tracker
Won't Fix
Votes
1
Found in
6000.0.58f1
6000.1.16f1
6000.2.7f1
Issue ID
UUM-122336
Regression
No
[Android][Vulkan] Memory leak on some Adreno devices when Graphics API is set to Vulkan
Steps to reproduce:
1. Open the “IN-98958” project
2. Build and Run
3. Wait for about 20 seconds
Expected result: The Player doesn’t crash
Actual result: The Player crashes
Reproducible with: 6000.0.58f1, 6000.1.16f1, 6000.2.7f1, 6000.3.0b2
Not reproducible with: 6000.3.0b4, 6000.4.0a1
Fixed in: 6000.3.0b3
Testing environment: macOS 15.3.2 (M4 Pro), macOS 15.3.2 (M2) (by user)
Not reproducible on: No other environment tested
Reproducible with these devices:
VLNQA00640 - Samsung Galaxy S25 Ultra (SM-S938B), CPU: Snapdragon 9 Elite (SM8750), GPU: Adreno 830, OS: 15
Galaxy s24, GPU: Adreno (by user)
Galaxy Z Fold7 SC-56F (by user)
Not reproducible with these devices:
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11
VLNQA00642 - Google Pixel 9a (Pixel 9a), CPU: -, GPU: Mali-G715, OS: 15
Pixel 9, GPU: Tensor G4 (by user)
Notes:
- Doesn’t reproduce with devices other than Adreno GPU
- Sometimes, the Player does not go past the Splash Screen
- Reproducible with Vulkan Graphics API but not with OpenGLES3
- Use Autoconnect Profiler to see the memory climb
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
The fix is available in 6.3 and it is risky to backport it to 6.0. Customer mentioned that they will upgrade their project to 6.3.