Artem Kharytoniuk

@danginsburg I removed the restriction, more people agree now that it makes sense. The initial version of `vkCmdBuildAccelerationStructuresKHR` validatiotion will be in the new SDK, so I'm closing this, please...

UPDATE: `VUID-vkGetMemoryFdPropertiesKHR-fd-00673` description was changed in 1.3.251 to this: `fd must point to a valid POSIX file descriptor memory handle`. ~~UPDATE: `VUID-vkGetMemoryFdPropertiesKHR-fd-00673` is marked as unimplementable: https://github.com/KhronosGroup/Vulkan-ValidationLayers/commit/146705fefb56a92581bdfe20f8442dda3344f53b~~ ~~It does not...

@r-potter https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/8794 PR handles both the original use case from https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/6351 and also the situation you mentioned above (we had similar errors on our Android CI).

I assigned synchronization label because of queue thread but can also be video specific.

Going to add synchronization label back, it looks like there is still issue there.

@Goshido there is a limitation to the amount of information that can be provided for the `prior_usage` access, but it should be possible to provide resource information for the `submitted_usage`.

I'll try to add resource information to `submitted_usage`, does not look hard except I missed something. Adding more information to `prior_usage ` is much harder, this requires to store a...

@Goshido Going to postpone the fix. Doable, but need to update memory allocation scheme first. Implementation note: instead of allocating handle array per usage record, allocate single buffer per command...

@Goshido Support is added here https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/8222. Currently it's buffers only, images will be later after we test current solution for a bit.

> What happens is that **after a command buffer has executed**, any resources it uses are either returned to be reused or outright destroyed on a cleanup thread. This includes...