Search Issue Tracker
Won't Fix
Votes
1
Found in
2019.4
2020.3
2020.3.18f1
2021.1
2021.2
2022.1
Issue ID
1367351
Regression
No
[Vulkan] Considerable increase in memory over other Graphics APIs when using Vulkan on Windows
How to reproduce:
1. Open the attached user's project 'VulkanMeshTest.zip'
2. Build and Run the application on the Windows platform
3. When the app loads, open Windows Task Manager (press Ctrl + Shift + Esc)
4. In the Process tab of the Task Manager, inspect the memory of the 'VulkanMesh.Test.exe' process
Expected results: Memory is ~100 MB (comparing to other Graphics APIs)
Actual results: Memory is ~180 MB (almost double compared to OpenGLES
Reproducible with: 2019.4.30f1, 2020.3.19f1, 2021.1.22f1, 2021.2.0b13, 2022.1.0a11
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
- "Visual Effect Event Tester" Overlay is cut off when using the Scene View not in standard dimensions
- Visual Effect overlay has no tooltips for the playback controls
- Github link in the Rider tab of Preferences window has no padding on the left side and is not aligned with the other elements
- “Clear locked objects” button in the Info tab of the Physics Debugger window has no padding on the right side and has an extra space in between the words “locked” and “objects”
- Renaming the VFX Graph uses "Enter" for a new line and "Enter + Shift" to confirm instead of vice versa
Resolution Note (2022.1.X):
Discussion with Florian with regards to disparity supports the 'Won't Fix'