[vulkan] Debug report from ObjectType: 5
When launching a Walnut app, the console is spammed with these messages (these are the first four frames)
[vulkan] Debug report from ObjectType: 5
Message: Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR(): Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.290.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[vulkan] Debug report from ObjectType: 5
Message: Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0xdcc8fd0000000012, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR(): Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.290.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[vulkan] Debug report from ObjectType: 5
Message: Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR(): Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.290.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[vulkan] Debug report from ObjectType: 5
Message: Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0xdcc8fd0000000012, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR(): Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.290.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
Each frame the handle swaps between two values, 0x967dd1000000000e and 0xdcc8fd0000000012
The line i found caused the error is this line I also found this issue at the dear ImGui repo which seems related (same objectType, same handle)
This is a repost from an issue in WalnutAppTemplate, but as i stated there, the issue lies with Walnut, not with WalnutAppTemplate
I went to work on the project anyways, and i found calling Walnut::Image::SetData doesnt show the warning for that frame, checked by not calling it after a couple of frames, and when it is not called the errors return
important note i feel i need to add, as the logging of this message is only a debug message, running in release doesnt show this message
Same problem appeared after switching from 1050 Ti to 4090
Don't know if anyone is still having issues with this, but here is a quick fix for anyone dealing with issues regarding some [vulkan] Debug report from ObjectType: 5 related errors. There are multiple ways to handle this but if your just download an older sdk of Vulkan it should solve you problems. I personally just went back and used sdk version 1.3.126.0. If you prefer to use the most recent version of Vulkan this should fix your issue as well https://github.com/ocornut/imgui/issues/7236.
I added a wait on the semaphores that should fix this @ #90