DadSchoorse / vkBasalt

a vulkan post processing layer for linux
zlib License
1.24k stars 52 forks source link

vkBasalt_DestroyDevice and vkBasalt_DestroyInstance leak memory #27

Closed nicokoch closed 4 years ago

nicokoch commented 4 years ago

The functions vkBasalt_DestroyDevice and vkBasalt_DestroyInstance do not call the next layer's vkDestroy{Device,Instance}functions, which means that the corresponding objects will never get freed.

DadSchoorse commented 4 years ago

I fixed the DestroyDevice memory leak with 585561a35fb88ca201ac3b3bb8ff03af1baa08ef , but if I try to call DestroyDevice it segfaults. I do not know why it does that, so any help would be appreciated.