-
Notifications
You must be signed in to change notification settings - Fork 880
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
Unexpected DX12 Device Removal on Fence Creation #1382
Comments
Alright, we appear to be hitting a device removal (error code is 0x887A0005 DXGI_ERROR_DEVICE_REMOVED) some time before we call CreateFence, then the fence creation is exposing this removal. In order to diagnose this, we need to find the reason for device removal, which will involve running the program in the MSVC debugger to get the error message from the debug layers. This is for an old version of wgpu/gfx-backend-dx12 (current is 0.8) because iced hasn't updated yet, but there is a patch update available in the 0.7 train for gfx-backend-dx12, so you should try I should note that we should also hook into this debug information like we do the vulkan validation layers. (Filed #1383 for this problem) |
Closing as stale due to hal rewrite, please refile if it's still an issue. |
Treat expressions in `Function::named_expressions` like WGSL `let` declarations, assuming that the Load Rule was applied to the rhs of the declaration, meaning that their values are always `Indirection::Ordinary`. Split `write_expr_plain_form` out from `write_expr_with_indirection`, to clean up the parenthesis generation: no more `opened_paren` variable, just function calls. This makes the early return for named expressions neater. Fixes gfx-rs#1382.
Raising this as part of this issue, for OpenVehicleDiag
Description
Using the Iced GUI Library, it appears WGPU panics with the DX12 backend with the following stack trace:
Expected vs observed behavior
Program does not crash
The text was updated successfully, but these errors were encountered: