Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2019.4
2020.1
2020.1.10f1
2020.2
2021.1
Issue ID
1287057
Regression
No
[XR]][Vulkan][Quest1] Apps have significantly higher memory consumption on Vulkan compared to GLES3
Repro steps:
1. Open the user's attached project "VulkanTest.zip"
2. Make sure Graphics API is set to GLES
3. Build and Run on Quest1/2
4. When the app launches execute this command in the terminal “adb shell dumpsys meminfo -a com.DefaultCompany.VulkanTest”
5. Notice the amount of memory allocated for the app
6. Switch Graphics API to Vulkan
7. Repeat steps 3-5
Actual: The amount of memory used for the app when Vulkan is used is almost double
Reproducible with: 2019.4, 2020.1.15f1, 2020.2.0b13, 2021.1.0a7
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
- Crash on ConvertBufferToEXRBuffer when Lighting Generation is cancelled
- [URP] TrailEffect in URP package samples does not draw Trail Effect
- "NullReferenceException" error is thrown when calling UIDocument.runtimePanel in OnEnable with ExecuteInEditMode
- Graphics.Blit() performs the operation only to the last display when a multi-display environment is used
- [Windows] Multiple Separation Lines are present in the Light Create Menu
Resolution Note (fix version 2021.1):
Fixed on: 2021.1.7f1 and above
Resolution Note (fix version 2020.3):
Fixed on 2020.3.33f1