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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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!