vulkan-memory-leak-detector

Detect Vulkan memory leaks by analyzing resource lifetimes, RAII wrapper usage, and cleanup paths. This process verifies per-resource lifetime checks and validation-layer leak detection guidelines to surface unfreed allocations during development.

Vulkan applications leak memory during frames-in-flight execution when per-frame resource discipline is lacking. Enforcing per-frame resource duplication and proper synchronization prevents frame leaks caused by overlapping command buffer submissions.

Fix Vulkan Memory Allocator (VMA) leaks by verifying auto memory usage, persistent mapping, and dedicated allocations for large resources. Proper VMA integration checks ensure allocation pools are destroyed correctly during cleanup.

RAII Drop implementations are required to prevent Vulkan resource leaks by ensuring resources are wrapped and dropped automatically. RAII pattern validation confirms that memory handles are freed when objects leave scope.

This leak detection approach works with hot-reload workflows by enforcing hot-reload-safe cleanup. It ensures old pipeline and shader resources are properly destroyed when new ones are loaded during runtime.

The best way to find missing cleanup paths in Vulkan 1.3 codebases is running validation layers alongside RAII pattern validation. This combination surfaces unfreed resources and identifies missing Drop implementations across codebases.