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.
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
- GameObject doesn't execute animation the way it's supposed to until any GameObject in the Hierarchy is selected when in the Play Mode
- PropertyField does not properly render its field when changing it back from a valid Asset to "None"
- "ArgumentException: Input Button Enable Debug Button 1 is not set" is thrown when "Enable Debug Button 1" is deleted
- Duplicate invocations when Enabling InputActions during handling an input action
- "Assertion failed on expression" exceptions are thrown when using IJobParallelForTransformExtensions.RunReadOnly
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!