Vulkan render device leaks VkImageView when using WrapTexture.
Posted: 17 Jan 2026, 15:11
Hi,
This is about the Vulkan renderer provided in the native SDK 3.2.9 / 3.2.10.
When redirecting texture loads to the engine via a custom TextureProvider that calls WrapTexture, the resulting VKTexture has hash=0 and gets a VkImageView created in VKRenderDevice::TextureHash, eventually leaking it as VKRenderDevice is not responsible for cleaning up that texture.
Fixing it locally is not a big deal, so just wondering if there are any updates coming up.
This is about the Vulkan renderer provided in the native SDK 3.2.9 / 3.2.10.
When redirecting texture loads to the engine via a custom TextureProvider that calls WrapTexture, the resulting VKTexture has hash=0 and gets a VkImageView created in VKRenderDevice::TextureHash, eventually leaking it as VKRenderDevice is not responsible for cleaning up that texture.
Fixing it locally is not a big deal, so just wondering if there are any updates coming up.