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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
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!