Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Destroy failed when enable both vulkan backend and api validation #3

Closed
damnkk opened this issue May 20, 2024 · 2 comments
Closed

Destroy failed when enable both vulkan backend and api validation #3

damnkk opened this issue May 20, 2024 · 2 comments

Comments

@damnkk
Copy link

damnkk commented May 20, 2024

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. "
image
I obtained the allocation number and size of these leaked memories
image
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
@dzhdanNV
Copy link
Collaborator

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.

@damnkk
Copy link
Author

damnkk commented May 23, 2024

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 :-)

@damnkk damnkk closed this as completed May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants