Vulkan: Use of previously acquired images from retired Swapchains results in crash

[DarathDev]

Problem

An exception is thrown when performing any operation that involves an acquired image from a retired swapchain. Specifically, I have seen this behaviour with the creation of pipeline barriers, and present operations.

This seems to conflict with the Vulkan spec for VkSwapchainCreateInfoKHR

After oldSwapchain is retired, the application can pass to vkQueuePresentKHR any images it had already acquired from oldSwapchain. E.g., an application may present an image from the old swapchain before an image from the new swapchain is ready to be presented. As usual, vkQueuePresentKHR may fail if oldSwapchain has entered a state that causes VK_ERROR_OUT_OF_DATE_KHR to be returned.

The application can continue to use a shared presentable image obtained from oldSwapchain until a presentable image is acquired from the new swapchain, as long as it has not entered a state that causes it to return VK_ERROR_OUT_OF_DATE_KHR.

Steps to Reproduce:

1. Create a swapchain
2. Acquire an image
3. Create a new swapchain on the same surface, with the first swapchain as the parameter for oldSwapchain
4. Perform an operation with the acquired image (imageMemoryBarrier, present, etc.)

No validation errors are thrown prior.

Expected Behaviour

Either the operation succeeds, or in the case of VkQueuePresentKHR it returns a VkResult value that reflects the issue like VK_ERROR_OUT_OF_DATE_KHR

Apologies for not having a minimal reproducible sample.

Connected System Information

Driver Version: 25.10.13.01-250526a-416003C-AMD-Software-Adrenalin-Edition
GPUOpen Interface Major Version: 42

Operating System Name: Windows 11 Pro
Operating System Description: 26100.1.amd64fre.ge_release.240331-1435

GPUs:

---

Name: AMD Radeon RX 7900 XT

ASIC info

---

Device Id: 744C
Revision: CC
Family: 91
gfx_engine: 13

---

Name: AMD Radeon(TM) Graphics

ASIC info

---

Device Id: 164E
Revision: C3
Family: 95
gfx_engine: 13

DxDiag.txt

[DarathDev]

I have also tried leaving the oldSwapchain null, which should result in createSwapchain returning VK_ERROR_NATIVE_WINDOW_IN_USE_KHR, instead I get VK_ERROR_FORMAT_NOT_SUPPORTED

[pperucki-AMD]

Any chance of getting a sample code reproducing the issue? That would speed up having a fix done.

[DarathDev]

I'm using .NET bindings to the Vulkan Api, which I doubt is particularly useful for you.
On that note, while I doubt its an issue with with the bindings themselves, I cannot guarantee that.

[pperucki-AMD]

We weren’t able to reproduce this issue. Can you check if it still happens with the newest driver?
Would it be possible for you to provide a minimal project that exposes the problem? The .NET Vulkan binding is not a blocker — as long as the project can be compiled and run locally, we’ll be able to handle it.

[DarathDev]

I will try with the new driver, and if it still happens I will see about getting you a min repro.

[pperucki-AMD]

@DarathDev did you have a chance to check with the latest driver?

[DarathDev]

Sorry for the delay, I have checked with the latest driver and I still run into this issue. I've made a reproducible sample in Odin for Windows which rules out it being an issue with the bindings.

The most relevant code is found on lines 117-122 and 1160 - 1220

Sample