Forum Discussion
Windows KB5074109 breaks Vulkan resource interop
I and others unrelatedly have noticed a severe regression in Vulkan and interop with regard to the specification. An example of this is here on the Nvidia forums: https://forums.developer.nvidia.com/t/cuda-vulkan-image-interop-broken-on-windows/359258
Per the CUDA documentation, "On Linux and Windows 10, both dedicated and non-dedicated memory objects exported by Vulkan can be imported into CUDA." What appears to be happening is that Windows is incorrectly, for a random set of Vulkan external resources, not correctly addressing the resource. Setting it to dedicated appears to resolve this but not entirely. Given myself and others have resolved the issue by backing out KB5074109, the regression lies in how WDDM is managing shared resources between the driver and the OS. I hope this can be addressed.
Happy to provide a strawman example upon request.
3 Replies
Is there any way to fix this?
Thank you for sharing this detailed insight. It sounds like you're experiencing a significant regression in Vulkan and CUDA-OpenGL/Vulkan interoperability on Windows, particularly following recent updates like KB5074109. This kind of issue, especially involving low-level driver and OS interactions, can be quite complex and impactful for development workflows.
The update seems to interfere with the correct addressing and management of Vulkan external resources, especially shared or exported resources, leading to failures in resource import/export operations.
