-
Notifications
You must be signed in to change notification settings - Fork 969
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
SIGSEGV in shadow
test with Vulkan backend on Fedora
#3377
Comments
Output from wgpu-info: wgpu-info-wgpu#2277.txt |
shadow
example with Vulkan backend on Fedorashadow
test with Vulkan backend on Fedora
Since the stack trace shows the validation layers doing a memcpy to a null pointer, this may be a bug in the validation layers. (thx to cwfitzgerald) |
I suspect that Mesa commit 662e05c9 is the fix for this. |
It seems like, prior to the above fix, Mesa's
This means that there's no guarantee that the specific command buffer we're calling Trying to remove the nonexistent label causes the command buffer's label buffer's byte size to underflow to The next call to The Mesa commit above changes all the command buffer and queue label functions to use a utility function that checks whether the label buffer is empty before popping. |
It's hard to tell when the fix will make it into a new Mesa release. From what I can tell, it won't be included in the 23.0 branch, and we'll have to wait until 23.1 comes out in April to see a fix. |
Hmm. When I use
|
Okay, maybe the second time's a charm: in mesa commit 1c64952e seems to fix another aspect of this. That fix is not present on the |
We can't require users to update their copies of Mesa, so we're going to need a workaround for this. It should suffice to drop debug markers on the floor on Vulkan for specific Mesa versions. |
The following command crashes with a
SIGSEGV
on my machine:Stack trace
Package versions installed
I'm running Fedora 37 on x86_64 with the following vulkan RPMs installed:
The text was updated successfully, but these errors were encountered: