Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
Issue ID
1372610
Regression
No
[vulkan] Randomly assigned Material texture or buffer properties can cause huge memory usage
The DescriptorSet cache in the Vulkan backend has no maximum size and if descriptors are bound programmatically the cache may grow indefinitely if a shader has many texture or buffer bind points.
Comments (1)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- 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
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Roobubba
Jan 05, 2022 10:12
Will this fix be applied to 2020.3 LTS? I'm using ECS so cannot switch to a newer Unity version, and would like to resolve the issue mentioned in this thread: https://forum.unity.com/threads/vulkan-graphic-api-cause-out-of-memory.1080941/ so I can put out a linux build with my raymarching compute shaders.
Thanks in advance!