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
would crash on a shipping driver inside vkCmdDispatch. If the vkCmdSetLineWidth is removed, there's no crash. It would be good to add tests of setting dynamic state without ever doing graphics work (i.e. compute only, or transfer commands only), as well as intermingling graphics state setting with compute dispatches.
I'm not sure if it would be helpful but I've uploaded a zip with two renderdoc captures: dispatch_crash.zip, the first capture has just the dispatch and the second has the vkCmdSetLineWidth as well. Note that selecting the dispatch in renderdoc will crash if the driver has this bug, since RenderDoc will then add this call internally at some point (which is how the bug was found). The captures should open on any GPU since they require nothing more than vulkan 1.0 with no physical device features, and allocate no memory or anything else that might be device-specific.
The text was updated successfully, but these errors were encountered:
I ran into a driver crash where doing (sketched):
would crash on a shipping driver inside
vkCmdDispatch
. If thevkCmdSetLineWidth
is removed, there's no crash. It would be good to add tests of setting dynamic state without ever doing graphics work (i.e. compute only, or transfer commands only), as well as intermingling graphics state setting with compute dispatches.I'm not sure if it would be helpful but I've uploaded a zip with two renderdoc captures: dispatch_crash.zip, the first capture has just the dispatch and the second has the
vkCmdSetLineWidth
as well. Note that selecting the dispatch in renderdoc will crash if the driver has this bug, since RenderDoc will then add this call internally at some point (which is how the bug was found). The captures should open on any GPU since they require nothing more than vulkan 1.0 with no physical device features, and allocate no memory or anything else that might be device-specific.The text was updated successfully, but these errors were encountered: