Open
Description
vkDeviceWaitIdle must wait till all the work is done (even if device is lost), cause it's used to ensure that it is safe to delete logical device. Right now vkDeviceWaitIdle doesn't do anything if device is lost: MVKDevice::waitIdle uses MVKQueue::waitIdle which checks the state of device and if it is not VK_SUCCES, it returns immediately. This leads to this problem that I reported before. Also see answer of Nicol Bolas in this stackoverflow discussion, he also says that this is bug and if device is lost, vkDeviceWaitIdle still must perform work as usual.