-
Notifications
You must be signed in to change notification settings - Fork 779
Open
Labels
bugSomething isn't workingSomething isn't working
Description
While doing PR reviews I noticed that the calibrated timestamps samples crashes on my setup: Windows 11, Nvidia RTX 4070, recent drivers, latest Vulkan SDK.
Before the crash I see the following validation errors:
[error] -2001841718 - VUID-VkCalibratedTimestampInfoKHR-timeDomain-parameter: vkGetCalibratedTimestampsEXT(): pTimestampInfos[2].timeDomain (VK_TIME_DOMAIN_PRESENT_STAGE_LOCAL_EXT) requires the extensions VK_EXT_present_timing.
The Vulkan spec states: timeDomain must be a valid VkTimeDomainKHR value (https://docs.vulkan.org/spec/latest/chapters/synchronization.html#VUID-VkCalibratedTimestampInfoKHR-timeDomain-parameter)
[error] 867943797 - VUID-VkCalibratedTimestampInfoKHR-timeDomain-12227: vkGetCalibratedTimestampsEXT(): pTimestampInfos[2].timeDomain is VK_TIME_DOMAIN_PRESENT_STAGE_LOCAL_EXT but pNext (VkSwapchainCalibratedTimestampInfoEXT::pNext is NULL) does not contain VkSwapchainCalibratedTimestampInfoEXT.
The Vulkan spec states: If timeDomain is VK_TIME_DOMAIN_SWAPCHAIN_LOCAL_EXT or VK_TIME_DOMAIN_PRESENT_STAGE_LOCAL_EXT, the pNext chain must include a VkSwapchainCalibratedTimestampInfoEXT structure. (https://docs.vulkan.org/spec/latest/chapters/synchronization.html#VUID-VkCalibratedTimestampInfoKHR-timeDomain-12227)
The actual crash happens in the get_timestamps function when trying to call vkGetCalibratedTimestampsEXT.
This is crashing inside the driver, combined with above validation errors it seems the sample is doing something wrong.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working