Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Experiment with handling VK_LOST_DEVICE #17532

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from
Draft

Conversation

hrydgard
Copy link
Owner

The idea is to gracefully teardown and recreate the Vulkan device if this happens due to either emulator or driver bug.

Currently, we don't fully implement LostDevice/RestoreDevice for Vulkan (as called from Android task switching), as in reality we do keep around the same device. So we don't delete/recreate everything, just most things, and finding the last things might be tricky.

However I was able to get this working to some degree on Intel GPU on Windows. On NVIDIA, I can't seem to create a new device in the same process after I've crashed one.

So overall, this is a bit questionable. Might be better to try to root out the remaining causes of lost device, although it would be nice to have this as a safety net.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant