Dzmitry Malyshau

Oh interesting! We've seen (driver) issues with WARP before. I wonder if it's something to do with the way our mapping flush/invalidation works.

`get_current_frame` is meant to block on CPU until a frame of the swapchain can be retired. For FIFO this is the oldest frame, for Mailbox this is any frame. >...

Thank you for filing this! Hypothetically, here is what's happening: 1. Your system exposed NV GPU as well as a software implementation (lavapipe) 2. Our example defaults to "LowPower" preference....

Hmm, interesting. The power preference should already pick your NVidia instead of Lavapipe: ```rust let preferred_gpu = match desc.power_preference { PowerPreference::LowPower => integrated.or(other).or(discrete).or(virt).or(cpu), PowerPreference::HighPerformance => discrete.or(other).or(integrated).or(virt).or(cpu), }; ```

What does `wgpu-info` say?

EGL reports as unable to present to the window natively: > [2022-01-31T23:32:46Z WARN wgpu_hal::gles::egl] EGL says it can present to the window but not natively This may be due to...

@pythonesque just a heads up: the issue is moved into `wgpu`, but we are still very interested to get this fixed!

Thank you for filing! Please provide an [API trace](https://github.com/gfx-rs/wgpu/wiki/Debugging-wgpu-Applications#tracing-infrastructure), and I'll be happy to investigate quickly.

I :heart: that menu :)

Replaying this trace, I'm seeing 40 bytes updated, all the 5 instances are there:  @simast could you try to replay it yourself, using `wgpu`'s player? I wonder if it's...