Search Issue Tracker

Fixed in 2021.2.X

Fixed in 2020.3.X



Found in






Issue ID




[Android][Vulkan][Mono] The amount of memory allocated for textures on Vulkan is significantly higher compared to GLES3



Repro steps:
1. Open attached project
2. Make sure Vulkan is in use
3. Build and Run a dev build on Android

Actual: The "gfx memory" which displays Profiler.GetAllocatedMemoryForGraphicsDriver is double the size on Vulkan

Reproducible with: 2019.4.17f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0b1

Tested and reproduced with these devices:
VLNQA00225, Qualcomm null (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
----------, Oneplus OnePlus 6 (ONEPLUS A6003), Android 10, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
----------, Google Pixel 3 XL (Pixel 3 XL), Android 11, CPU: NOT FOUND, GPU: Adreno (TM) 630
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540

  1. Resolution Note (fix version 2021.2):

    Parts of this is still by design. The engine needs extra temp memory for a few frames. To get consistent results the script in the project would need to wait for a few frames after uploading the texture and then sample the memory usage.

  2. Resolution Note (fix version 2020.3):

    Fixed in: 2020.3.33f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.