Skip to content
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

Compute Benchmark Stalls due to Unresolving Future on Windows/Vulkan #677

Closed
cwfitzgerald opened this issue May 28, 2020 · 0 comments
Closed
Labels
type: bug Something isn't working

Comments

@cwfitzgerald
Copy link
Member

cwfitzgerald commented May 28, 2020

Description

The benchmark below will eventually stall due to a future that never properly resolves. This occurs on windows/vulkan and both intel and nvidia, but not linux/intel nor DX12/either.

Repro steps

Repo: https://github.com/cwfitzgerald/wgpu-heterogeneous-compute-benchmark/

Issue commit: 09ce658cd8e968d44efd511ff575ff6344d56b1b (branch wgpu-bug-677)

cargo bench -- 'gpu'

Should work out of the box. This will eventually stall. The time estimates given by criterion are fairly accurate, so if it's taking much longer than it's said, it is stalled. You can also add prints in the core benchmark loop here which will eventually stop printing.

You can add a excessively long sleep in the bench loop (100-1000ms) and the problem might go away.

Platform

wgpu-rs master
Win10 18362.836

@cwfitzgerald cwfitzgerald added the type: bug Something isn't working label May 28, 2020
kvark pushed a commit to kvark/wgpu that referenced this issue Jun 3, 2021
677: Update to latest wgpu master r=kvark a=yzsolt

- Update to latest `wgpu` master
- Fix build error caused by gfx-rs#1077

Co-authored-by: Zsolt Bölöny <bolony.zsolt@gmail.com>
@cwfitzgerald cwfitzgerald closed this as not planned Won't fix, can't repro, duplicate, stale Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant