Test memory leaks in vkEnumeratePhysicalDevices

This change adds dedicated test that checks if vkEnumeratePhysical- Devices does same amount of memory frees as it does allocations. Additionally alloc_callback_fail tests were changed so that if object construction was not successful with given number of allocations it is attempted one more time with 10000 allowed allocations. This will mainly affect instance and device creation tests as they require many allocations and with this we will be able to detect possible memory leaks. Components: Vulkan VK-GL-CTS issue: 149 Affects: dEQP-VK.api.device_init.enumerate_devices_alloc_leak dEQP-VK.api.object_management.alloc_callback_fail.* Change-Id: Ic64054a0753a4ba4fdf3e7ef3104787bf5d2a72b
robclark · Apr 18, 2020 · b9a868b · b9a868b
1 parent 015649c
commit b9a868b
Show file tree

Hide file tree

Showing 5 changed files with 83 additions and 7 deletions.
diff --git a/android/cts/master/vk-master-2020-03-01.txt b/android/cts/master/vk-master-2020-03-01.txt
diff --git a/android/cts/master/vk-master.txt b/android/cts/master/vk-master.txt
diff --git a/external/vulkancts/modules/vulkan/api/vktApiDeviceInitializationTests.cpp b/external/vulkancts/modules/vulkan/api/vktApiDeviceInitializationTests.cpp
diff --git a/external/vulkancts/modules/vulkan/api/vktApiObjectManagementTests.cpp b/external/vulkancts/modules/vulkan/api/vktApiObjectManagementTests.cpp
diff --git a/external/vulkancts/mustpass/master/vk-default.txt b/external/vulkancts/mustpass/master/vk-default.txt