Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.0b9
Issue ID
922705
Regression
No
Windows Standalone build uses twice the RAM on Vulkan than on D3D11
Windows Standalone build uses twice the RAM on Vulkan than on D3D11. Scene with Main Camera and Directional Light (newly created) uses ~60MB when built for D3D11 vs ~110MB when built for Vulkan.
Reproduction steps:
1. Create new project
2. Set graphics API for Windows to Direct3D11
3. Build and run
4. Observe the RAM usage in Task Manager
5. Close the player
6. Set graphics API for Windows to Vulkan
7. Build and run
8. Observe the RAM usage in Task Manager
Reproduced on: 5.6.0a1, 5.6.2p1, 2017.1.0b9, 2017.1.0f2, 2017.2.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
Add comment