From db31a54c64f14a89d64245ee4d3b31fdad82acf9 Mon Sep 17 00:00:00 2001 From: Tobin Ehlis Date: Wed, 13 Jan 2016 14:45:14 -0700 Subject: layers: MR129, Remove incorrect asserts from param_checker and object_tracker For apps that run with multiple instances, it's perfectly valid to have instances remaining at DestroyInstace() time so removing that assert from param_checker. Also, the assert appears to have been cut-and-pasted into DestroyDevice of both param_checker and object_tracker. The same logic applies for apps that use multiple devices. Running vulkancts with layers enabled found these issues. --- layers/param_checker.cpp | 2 -- 1 file changed, 2 deletions(-) (limited to 'layers/param_checker.cpp') diff --git a/layers/param_checker.cpp b/layers/param_checker.cpp index 58999acb..06842907 100644 --- a/layers/param_checker.cpp +++ b/layers/param_checker.cpp @@ -1795,7 +1795,6 @@ VK_LAYER_EXPORT VKAPI_ATTR void VKAPI_CALL vkDestroyInstance( layer_data_map.erase(pTable); pc_instance_table_map.erase(key); - assert(pc_instance_table_map.size() == 0 && "Should not have any instance mappings hanging around"); } bool PostEnumeratePhysicalDevices( @@ -2067,7 +2066,6 @@ VK_LAYER_EXPORT VKAPI_ATTR void VKAPI_CALL vkDestroyDevice( get_dispatch_table(pc_device_table_map, device)->DestroyDevice(device, pAllocator); pc_device_table_map.erase(key); - assert(pc_device_table_map.size() == 0 && "Should not have any instance mappings hanging around"); } bool PostGetDeviceQueue( -- cgit v1.2.3