Open Trider12 opened 1 month ago
@Trider12 thanks for reporting this, we are currently heavily working and fixing GPU-AV, once I get the new descriptor indexing validation setup, will come back and take a look, but hopefully it will "just be fixed" then
@Trider12 so I was able to reproduce the crash in https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/8535 (thanks for the simple breakdown of the tests)
So I see what is happening, we are mismatching the pipeline layout underneath we use in GPU-AV and creating an invalid Vulkan flow, which causes the crash... will try hard to get in before the next SDK soon!
Environment:
Describe the Issue
I have two graphics pipelines - A and B. A uses sets X and Y, B uses set X. X and Y are bound to sets 0 and 1 respectively. Here's the code:
Submitting this command buffer results in
VK_ERROR_DEVICE_LOST
with descriptors indexing validation enabled. There's no error with it disabled. The error can be avoided by creating pipeline B with pipeline layout A.According to the spec my usage is fine, because layouts A and B are compatible for set 0:
Expected behavior
Device not being lost.
Additional context
There are no validation errors prior to
VK_ERROR_DEVICE_LOST
.