Open Bug 1713151 Opened 3 years ago Updated 5 months ago

Tooling for debugging WebGPU presentation

Categories

(Core :: Graphics: WebGPU, enhancement, P5)

Product:
Core
Component:
Graphics: WebGPU
Type:
enhancement

Tracking

()

People

(Reporter: kvark, Unassigned)

References

(Blocks 1 open bug)

Details

Presentation in WebGPU is a complex topic. It involves tight cooperation between WebGPU content side, server side, and WebRender. It's also fully on C++ side, so Rust tooling doesn't help there. We need a good way to diagnose presentation issues.

Ideally, we want the performance markers for each frame:

  1. when it's requested by JS
  2. when the GPU callback is issued, and we copy the data from it
  3. when WR locks the external texture
  4. when the frame is actually presented
See Also: → 1713177
Blocks: webgpu-v1
Priority: -- → P3
Blocks: webgpu-phase-2
No longer blocks: webgpu-v1
Blocks: webgpu-triage
No longer blocks: webgpu-triage
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.