You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Initialize function,if I set the graphic API to Vulkan ,enable APIValidation, and call InitUI(...) at the end of the function, I will get the fatal error "DestroyDebugAllocator() failed: allocatedSize is not 0." because of a small piece of leaked memory when the program is destroyed. "
I obtained the allocation number and size of these leaked memories
After rigorous analysis, I can absolutely guarantee that these memories do not come from undestructed vulkan objects.
I hope someone can help me analyze what I did wrong, or is there a hidden bug in the framework? (Unlikely)
Any help is greatly appreciated:)
backend
enableAPIValidation
leak
VULKAN
✔
✔
VULKAN
x
x
D3D12
✔
x
D3D12
x
x
The text was updated successfully, but these errors were encountered:
Hi! The leak most likely comes from the VK validation layer. Please, update to the VK SDK to v1.3.283 or newer and try again. I will update NRI and related projects to the latest today. I can't reproduce this issue anymore.
Hi! The leak most likely comes from the VK validation layer. Please, update to the VK SDK to v1.3.283 or newer and try again. I will update NRI and related projects to the latest today. I can't reproduce this issue anymore.
thank you, the error not come out after I update the vulkan SDK :-)
In the Initialize function,if I set the graphic API to Vulkan ,enable APIValidation, and call InitUI(...) at the end of the function, I will get the fatal error "DestroyDebugAllocator() failed: allocatedSize is not 0." because of a small piece of leaked memory when the program is destroyed. "
I obtained the allocation number and size of these leaked memories
After rigorous analysis, I can absolutely guarantee that these memories do not come from undestructed vulkan objects.
I hope someone can help me analyze what I did wrong, or is there a hidden bug in the framework? (Unlikely)
Any help is greatly appreciated:)
The text was updated successfully, but these errors were encountered: