Is possible to destroy the VmaAllocator without it trying to make any Vulkan calls. about vulkanmemoryallocator

[adam-sawicki-a]

This is not something that the library was designed for. By design, lifetime of VmaAllocator should be scoped inside of lifetime of VkDevice, just as lifetime of any VmaAllocation object, as well as VkDeviceMemory blocks managed internally by the allocator, is scoped inside lifetime of the allocator.

Destroying Vulkan device object without notifing code that uses it, as well as leaking memory or API objects looks like bad software design. Even in case of Vulkan device loss, it's still possible to properly destroy all its objects.

If you really want to add this feature, possibly the easiest way is to fill VmaAllocatorCreateInfo::pVulkanFunctions with pointers to your own functions, which you implement to either dispatch the call to real Vulkan function or discard it in case you lost access to Vulkan device.

The only Vulkan function that may be called during destruction of VmaAllocator is vkFreeMemory (and vkUnmapMemory, in case you also have some VmaAllocation objects left that are mapped or persistently mapped).