You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Commit bc65135 introduced a crash (Filament panic) when destroying and re-creating a swap chain using the Vulkan backend. I noticed the crash after pulling in recent Filament changes, and then bisected it to this commit. For me it is deterministically reproducible. The commit before this does not ever crash.
I ran it in a debugger; I'm not sure what info you might need but the line it crashes on is:
L249: VkResult result = vkCreateSwapchainKHR(mDevice, &createInfo, VKALLOC, &mSwapchain);
The error is:
Exception has occurred: CPP/_com_error
Exception thrown at 0x00007FFCD5EFFA4C in Anukari.exe: Microsoft C++ exception: _com_error at memory location 0x000000F63378EC70.
I tried to figure out what 0x000000F63378EC70 was supposed to be pointing to, but it wasn't obvious to me.
The error in the panic message is VK_ERROR_NATIVE_WINDOW_IN_USE_KHR, which makes me think that destroy() on the swap chain is not fully destroying it?
Describe the bug
Commit bc65135 introduced a crash (Filament panic) when destroying and re-creating a swap chain using the Vulkan backend. I noticed the crash after pulling in recent Filament changes, and then bisected it to this commit. For me it is deterministically reproducible. The commit before this does not ever crash.
I ran it in a debugger; I'm not sure what info you might need but the line it crashes on is:
L249: VkResult result = vkCreateSwapchainKHR(mDevice, &createInfo, VKALLOC, &mSwapchain);
The error is:
I tried to figure out what 0x000000F63378EC70 was supposed to be pointing to, but it wasn't obvious to me.
The error in the panic message is VK_ERROR_NATIVE_WINDOW_IN_USE_KHR, which makes me think that destroy() on the swap chain is not fully destroying it?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No crash.
Screenshots
N/A
Logs
Desktop (please complete the following information):
Smartphone (please complete the following information):
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: