Vulkan - Fix display surface lost error #16887
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does the pull request do?
Fix vulkan rendering issue when a vulkan surface is destroyed while the application is still running. This is done by disposing the old surface and recreating it and the swapchain.
What is the current behavior?
When a window is no longer valid for a vulkan surface, vulkan throws a VK_ERROR_SURFACE_LOST_KHR error and the surface can no longer be rendered on to. This is very common on Android where any android surface, which acts as a native window, is destroyed when the app suspends.
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues
Fixes #16718