59d0422dcd
PR #90993 added several debugging utilities. Among them, advanced memory tracking through the use of custom allocators and VK_EXT_device_memory_report. However as issue #95967 reveals, it is dangerous to leave it on by default because drivers (or even the Vulkan loader) can too easily accidentally break custom allocators by allocating memory through std malloc but then request us to deallocate it (or viceversa). This PR fixes the following problems: - Adds --extra-gpu-memory-tracking cmd line argument - Adds missing enum entries to RenderingContextDriverVulkan::VkTrackedObjectType - Adds RenderingDevice::get_driver_and_device_memory_report - GDScript users can easily check via print( RenderingServer.get_rendering_device().get_driver_and_device_memory_report() ) - Uses get_driver_and_device_memory_report on device lost for appending further info. Fixes #95967 |
||
|---|---|---|
| .. | ||
| SCsub | ||
| rendering_context_driver_vulkan.cpp | ||
| rendering_context_driver_vulkan.h | ||
| rendering_device_driver_vulkan.cpp | ||
| rendering_device_driver_vulkan.h | ||
| vulkan_hooks.cpp | ||
| vulkan_hooks.h | ||