1937100 - Content stutters from `CommandEncoder` and `ComputePipeline` DOM object destruction in `Marching Cubes` example from official WebGPU samples

Status: NEW

(Core :: Graphics: WebGPU, defect, P1)

Description

[Erich Gubler [:ErichDonGubler] (he/him)]

Steps to reproduce

1. Open https://webgpu.github.io/webgpu-samples/?sample=marchingCubes. Observe that while the demo runs, occasional stutter on the order of a hundred milliseconds occurs, interrupting multiple render frames.

Comment 1

[Erich Gubler [:ErichDonGubler] (he/him)]

Originally found while re-triaging bug 1806659.

Comment 2

[Erich Gubler [:ErichDonGubler] (he/him)]

Made a profile here: https://share.firefox.dev/3ZP11Qy

Comment 3

[Corentin Wallez]

FYI we had a similar issue in Chromium on GC because many GPUCommandBuffers get released at once, which all have O(commands) cost to that. The solution was to eagerly destroy them after submit (they are consumed even if the submit is an error for that reason IIRC).

Comment 4

[Teodor Tanasoaia [:teoxoy]]

We do consume the content of command buffers on submit, so it's probably something else.

Comment 5

[Corentin Wallez]

IIRC Firefox uses content-side tracking of objects used by the command buffers. So even if the command buffers are consumed on submit on the GPU process side, if they aren't on the content-process, it could cause stutters.

Comment 6

[Teodor Tanasoaia [:teoxoy]]

Good point, we do hold references to objects https://searchfox.org/mozilla-central/rev/04a2c5317c0af560ed1689304498416c9c6c485a/dom/webgpu/RenderPassEncoder.h#56-60 that we don't clear on encoder.end().

Comment 7

[Teodor Tanasoaia [:teoxoy]]

With the shader cache https://github.com/gfx-rs/wgpu/pull/7729 the sample runs a lot smoother with occasional hitches due to GC, see https://share.firefox.dev/3FubZUh.

Based on the new profile I don't think this needs to be blocked on Bug 1968122 anymore.