UI freeze on Linux/vulkan replay

[kvark]

Description

Capturing and replaying a relatively simple workload freezes the UI and makes it unusable.

Steps to reproduce

• download and unpack wgpu-trace.zip
• download and unpack wgpu.zip
• cd wgpu/player
• cargo build --features renderdoc - this may take a bit of time, requires Cargo + Rust. The artifact we are interested in is ../target/debug/play, and that's what we'll be running from renderdoc, passing the wgpu-trace path as a parameter.
• launch the app from Renderdoc using the following settings:
  

You'd need to change the paths to wgpu and wgpu-trace. It will finish quickly and produce a capture automatically.
Navigating to the draw call (EID 43, for example, and then to EID 9) would show the progress bar at the bottom, which never stops and freezes the UI:

The application stops responding and can only be killed after that.

Environment

• RenderDoc version: 1.10
• Operating System: Solus linux
• Graphics API: Vulkan

[baldurk]

Can you share the capture itself that hangs? I can more easily look into that since it means I won't have to figure out how to set up cargo + rust. If not that's fine it might just be a little longer before I can repro this.

[kvark]

Here we go: renderdoc-bug-capture.zip

[baldurk]

This seems like it may be the same as #1863 . I can replay the capture fine with latest mesa on my hardware, but looking at it I can see that your application still maps memory behind GPU render targets and there was a bug that meant renderdoc was still replaying mapped memory updates into that.

Please try again with that commit, if it still doesn't work let me know and I can investigate again. If it does still happen I'd particularly be interested to know if it still happens on your nvidia card, or on intel if you don't map memory with render targets bound.

[kvark]

I confirm your fix works. Thanks for the quick turnaround (and unblocking me)! 🥇