Don't leak ref to native handle in external memory tests
authorChris Forbes <chrisforbes@google.com>
Thu, 3 May 2018 22:03:53 +0000 (15:03 -0700)
committerChris Forbes <chrisforbes@google.com>
Thu, 3 May 2018 22:06:40 +0000 (15:06 -0700)
Based on a later revision to https://gerrit.khronos.org/#/c/2455

Bug: b/79216732
Change-Id: I4aab353d1d9a8ecb818c682b60d274ce82ef6d38
Affects: dEQP-VK.api.external.memory.android_hardware_buffer.*
Components: Vulkan
Test: CtsDeqpTestCases

external/vulkancts/modules/vulkan/vktExternalMemoryUtil.cpp

index e08c2d5f73a74be238b80a6b5aeab0d0df09cd1a..b7e20959b1ed3cc3526e57cba0381957f062413e 100644 (file)
@@ -1044,8 +1044,6 @@ static vk::Move<vk::VkDeviceMemory> importMemory (const vk::DeviceInterface&
                };
                vk::Move<vk::VkDeviceMemory> memory (vk::allocateMemory(vkd, device, &info));
 
-               handle.disown();
-
                return memory;
        }
 #endif // (USE_ANDROID_O_HARDWARE_BUFFER)