diff options
| author | Tobin Ehlis <tobine@google.com> | 2016-01-13 14:45:14 -0700 |
|---|---|---|
| committer | Mark Lobodzinski <mark@lunarg.com> | 2016-01-14 10:03:15 -0700 |
| commit | db31a54c64f14a89d64245ee4d3b31fdad82acf9 (patch) | |
| tree | 3678ce09241155b1ff9a010ae45a6566885196cd /layers/param_checker.cpp | |
| parent | cee3480739a5bda2a239508944b43abe71eb5874 (diff) | |
| download | usermoji-db31a54c64f14a89d64245ee4d3b31fdad82acf9.tar.xz | |
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.
Diffstat (limited to 'layers/param_checker.cpp')
| -rw-r--r-- | layers/param_checker.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
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( |