Don't disown Win32 handle after import
authorPiers Daniell <pdaniell@nvidia.com>
Wed, 3 Apr 2019 20:20:09 +0000 (14:20 -0600)
committerPiers Daniell <pdaniell@nvidia.com>
Wed, 3 Apr 2019 20:22:04 +0000 (14:22 -0600)
commit37547c29a94c1499341918d7558dfbf685429e4b
treedfbdf3d54201d088ec07d9cc09b4ff7e393b7414
parente1a2278f10f043c2075e8133a2abf51b78d0b975
Don't disown Win32 handle after import

For Win32 fences and semaphores, the Vulkan implementation does not take
ownership of the handle after import. It is up to the application to
maintain ownership while the handle is in use and to call
CloseHandle() after.

Affects:
dEQP-VK.api.external.*.opaque_win32*

Components: Vulkan

VK-GL-CTS issue: 1720

Change-Id: I4e26ef53c9bf27c30efd71992fd02a574f81b3a0
external/vulkancts/modules/vulkan/api/vktApiExternalMemoryTests.cpp
external/vulkancts/modules/vulkan/vktExternalMemoryUtil.cpp