1877010 - Fiddling with the parameters of a webgpu demo freezes the browser UI (with no CPU/GPU/RAM use)

Status: RESOLVED FIXED

(Core :: Graphics: WebGPU, defect)

Description

[Mayank Bansal]

Go to https://react-webgpu-samples.vercel.app/
Rapidly fiddle with the first slider

AR: The browser UI freezes.
ER: Not so

Regression range:
Bug 1869931 - Remove RemoteTexture push callback r=gfx-reviewers,lsalzman

WebGPU rendering needs to be synchronized to dom like WebGL and canvas 2D. But the current rendering is not synchronized to dom.

Differential Revision: https://phabricator.services.mozilla.com/D197326

Comment 1

[Mayank Bansal]

Profile with graphics+WebGPU logging : https://share.firefox.dev/3HxU1hc

Comment 2

[Mayank Bansal]

Attachment: about:support

Comment 3

[BugBot [:suhaib / :marco]]

Set release status flags based on info from the regressing bug 1869931

Comment 4

[Sotaro Ikeda [:sotaro]]

I Confirmed that RemoteTextureOwner was unregistered before Pushing remote texture by WebGPUParent::RecvSwapChainDrop()

Comment 5

[Sotaro Ikeda [:sotaro]]

Attachment: Bug 1877010 - Defer unregistering RemoteTextureOwner if it is not confirmed by ImageHost

Comment 6

[Lee Salzman [:lsalzman]]

Attachment: Bug 1877010 - Track forwarder transaction ids for RemoteTextureMap with WebGL and WebGPU. r?sotaro

Comment 7

[Sotaro Ikeda [:sotaro]]

Assigned to : lsalzman, since he created the fix for the bug.

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/06c07b1488ab
Track forwarder transaction ids for RemoteTextureMap with WebGL and WebGPU. r=sotaro

Comment 9

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/06c07b1488ab

Comment 10

[Simona Badau, Desktop Test Engineering]

I could reproduce the initial issue on Windows 10 x64 using Nightly 124.0a1 (Build ID: 20240128091600) and I can confirm that the browser UI does no longer freeze on Nightly 125.0a1 (20240222103314).

However, I can't confirm the fix on Firefox 124.0b2 where the WebGPU sample it not rendering.
@Lee, is this expected in any way? Are there any additional settings that I should set? Could it be due to Bug 1879560, even if this seems to not be reproducible on Windows 10?

Comment 11

[Lee Salzman [:lsalzman]]

That's probably just bug 1879560, yes.