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
- Color picker does not show the correct color when selecting color on the moving object
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
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!