-
Notifications
You must be signed in to change notification settings - Fork 1k
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
"No work has been submitted for this frame" timeout #3189
Comments
I don't really understand why we need the #1892 (PR that introduced the flag) mentiones:
Considering #1688 has been merged, can we get rid of @cwfitzgerald do you have more context for this (since you reviewed #1892)? |
When no work is submitted for a frame, presenting the surface results in a timeout due to no work having been submitted. Fixes gfx-rs#3189. This flag was added in gfx-rs#1892 with a note that it was going to be temporary until gfx-rs#1688 landed.
When no work is submitted for a frame, presenting the surface results in a timeout due to no work having been submitted. Fixes gfx-rs#3189. This flag was added in gfx-rs#1892 with a note that it was going to be temporary until gfx-rs#1688 landed.
When no work is submitted for a frame, presenting the surface results in a timeout due to no work having been submitted. Fixes gfx-rs#3189. This flag was added in gfx-rs#1892 with a note that it was going to be temporary until gfx-rs#1688 landed.
Description
If you do not submit any work for a surface, and present it, problems occur running wgpuSwapChainGetCurrentTextureView (wgpu-native), it seems to be hitting this line specifically
Repro steps
You can just strip out all code that submits work from any rendering example
Expected vs observed behavior
Nothing should happen, and wgpuSwapChainGetCurrentTextureView should run just fine, but it does not, sometimes failing with a timeout, sometimes working
Extra materials

the 'beginning scene' is where i get the swap chain's current texture view, things marked with 'CallbackError' are errors from wgpuDeviceSetUncapturedErrorCallback
Platform
Arch Linux, AMD GPU, latest master of wgpu-native
The text was updated successfully, but these errors were encountered: