Skip to content

VkSemaphore memory leak when calling vkDestroyDevice() #81

Description

@Waqar-ukaea

I am seeing the following error when an application calls gprtContextDestroy() and hence vkDeviceDestroy():

ERROR: [1215490720][VUID-vkDestroyDevice-device-05137] : vkDestroyDevice(): Object Tracking - For VkDevice 0x5cb7b5335520, VkSemaphore 0xb000000000b has not been destroyed.
 The Vulkan spec states: All child objects created on device that can be destroyed or freed must have been destroyed or freed prior to destroying device (https://vulkan.lunarg.com/doc/view/1.4.313.0/linux/antora/spec/latest/chapters/devsandqueues.html#VUID-vkDestroyDevice-device-05137)
It doesn't cause tests to fail or anything like that. Just ouputs this vulkan error on application exit

In our library XDG I have recently updated the commit our git submodule for GPRT is pointing to from 6665d24 to
1e28356. So I can say that something has changed between these two commits to cause this problem.

It has no effect on the application during runtime and the error only happens during our application's exit when we call gprtContextDestroy().

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions