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

[vulkan] Debug report from ObjectType: 5 #15

Open
Daigoro96 opened this issue Jun 3, 2024 · 2 comments
Open

[vulkan] Debug report from ObjectType: 5 #15

Daigoro96 opened this issue Jun 3, 2024 · 2 comments

Comments

@Daigoro96
Copy link

I keep getting a lot of console output, mostly this one repeating over and over again:

[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.275.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)

@Jonathan523
Copy link

Same problem.

@ThunderSphun
Copy link

I got the problem as well
I get two handles swapping each other each frame,
frame 1 has this handle: 0x967dd1000000000e
frame 2 has this handle: 0xdcc8fd0000000012

for the rest the entire message is the same
a quick google for this debug error got me to this thread from dear ImGui which might be the issue, although, the place where the error takes place only uses the imgui vulkan window implementation (line which causes the error)
also, the error specificly states

The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending

and the line which causes the error uses VK_NULL_HANDLE. there are only things stated when it is not VK_NULL_HANDLE

I think this is either an issue with dear ImGui, or vulkan where walnut needs to find a workaround for, as this is a Walnut issue, and not a WalnutAppTemplate issue

Im gonna open a post there and link to this one, as it should be fixed there

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

No branches or pull requests

3 participants