-
Notifications
You must be signed in to change notification settings - Fork 943
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
Deadlock with 0.18 #4885
Comments
Could you try this again with trunk? We just fixed a few possible deadlocks - if it reproduces with the same stacks, I will investigate. |
That won't be easy - we're still on 0.18.x, and AFAIK there were some nontrivial API changes in |
It takes the ecosystem (specifically naga-oil and egui for us) a long while to update too, so even when trunk is out it may not be viable for us for a while :( |
Yeah, even the arcanization PR I was only able to test (around when it got merged) by ripping out |
Not trivially unfortunately, as arcanization totally shook up wgpu-core internals and these issues very much depend on it. |
Well then, I suppose, back to waiting for 0.19, and for the ecosystem to update to it? 🙃 |
I was able to test on current |
Amazing news! |
Description
We're getting regular deadlocks running some of our visual tests of Ruffle after upgrading to v0.18 (ruffle-rs/ruffle#13732), both on GitHub Actions, and our local machines.
Repro steps
Expected vs observed behavior
Expected: No deadlock ever.
Observed: Eventual deadlock.
Extra materials
Attached are the parts of 8 deadlocked test runner threads' stack traces deemed relevant.
Thread 1
Thread 2
Thread 3
Thread 4
Thread 5
Thread 6
Thread 7
Thread 8
Platform
Fedora Linux 39, Rust 1.74, Mesa 23.2.1, Ryzen 9 5950X, AMD Radeon RX 6600 XT (navi23, LLVM 16.0.6, DRM 3.54, 6.6.4-200.fc39.x86_64)
wgpu: branch
v0.18
, commit e16f7b4, mostly due to #4693, but also #4778.The text was updated successfully, but these errors were encountered: