commit a53702cbe2289b3c37f0904290ad2b03f703d0df
author Adam Sawicki <adam.sawicki@amd.com> Mon Nov 13 13:59:23 2023 +0100
committer Adam Sawicki <adam.sawicki@amd.com> Mon Nov 13 13:59:23 2023 +0100
tree 39244623490d073aa869539fb71d1d016918f3d3
parent b721922bce0e536c84b70a1d9bcd5db2b66e42df

More fixes based on #385

Thanks @alecazam

include/vk_mem_alloc.h

diff --git a/include/vk_mem_alloc.h b/include/vk_mem_alloc.h
index 3429315..b8795dc 100644
--- a/include/vk_mem_alloc.h
+++ b/include/vk_mem_alloc.h
@@ -888,7 +888,7 @@
 
 Use value `VK_NULL_HANDLE` to represent a null/invalid allocation.
 */
-VK_DEFINE_NON_DISPATCHABLE_HANDLE(VmaVirtualAllocation)
+VK_DEFINE_NON_DISPATCHABLE_HANDLE(VmaVirtualAllocation);
 
 /** @} */
 
@@ -3221,7 +3221,7 @@
 
 #ifndef _VMA_FORWARD_DECLARATIONS
 // Opaque handle used by allocation algorithms to identify single allocation in any conforming way.
-VK_DEFINE_NON_DISPATCHABLE_HANDLE(VmaAllocHandle)
+VK_DEFINE_NON_DISPATCHABLE_HANDLE(VmaAllocHandle);
 
 struct VmaMutexLock;
 struct VmaMutexLockRead;
@@ -11799,7 +11799,7 @@
 VmaDeviceMemoryBlock::~VmaDeviceMemoryBlock()
 {
     VMA_ASSERT_LEAK(m_MapCount == 0 && "VkDeviceMemory block is being destroyed while it is still mapped.");
-    VMA_ASSERT(m_hMemory == VK_NULL_HANDLE);
+    VMA_ASSERT_LEAK(m_hMemory == VK_NULL_HANDLE);
 }
 
 void VmaDeviceMemoryBlock::Init(
@@ -11846,7 +11846,7 @@
     // Hitting it means you have some memory leak - unreleased VmaAllocation objects.
     VMA_ASSERT_LEAK(m_pMetadata->IsEmpty() && "Some allocations were not freed before destruction of this memory block!");
 
-    VMA_ASSERT(m_hMemory != VK_NULL_HANDLE);
+    VMA_ASSERT_LEAK(m_hMemory != VK_NULL_HANDLE);
     allocator->FreeVulkanMemory(m_MemoryTypeIndex, m_pMetadata->GetSize(), m_hMemory);
     m_hMemory = VK_NULL_HANDLE;