Closed Bug 1878534 Opened 2 years ago Closed 3 months ago

[WebGPU] On "ResizeCanvas" webgpu-samples demo, the scrolling is very stuttery (without using lots of CPU/GPU) and leads to 2.5GB+ memory use

Categories

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

Product:
Core
Component:
Graphics: WebGPU
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1922992

People

(Reporter: mayankleoboy1, Unassigned)

References

(Blocks 2 open bugs,
URL
)

Details

Attachments

(1 file)

about:support
44.43 KB, text/plain
Details

Go to https://webgpu.github.io/webgpu-samples/samples/resizeCanvas
While the canvas is resizing, try to scroll the page using the touchpad

AR: https://share.firefox.dev/48XIIuL

The scrolling is stuttery. The demo doesnt seem to use a lot of cpu/gpu.

with the dx12-no-readback thingy, the profile is quite smooth
https://share.firefox.dev/3w9VWpy

Attached file about:support —

in both the above scenarios (dx12-no-readback enabled/disabled), occasionally the memory use increases to 2.5GB+

Summary: [WebGPU] On https://webgpu.github.io/webgpu-samples/samples/resizeCanvas scrolling is stuttery withput using lots of CPU/GPU, while the canvas is resizing → [WebGPU] On a WebGPU demo, while the canvas resizes the scrolling is very stuttery (without using lots of CPU/GPU) and sometimes leads to 2.5GB+ memory use
Summary: [WebGPU] On a WebGPU demo, while the canvas resizes the scrolling is very stuttery (without using lots of CPU/GPU) and sometimes leads to 2.5GB+ memory use → [WebGPU] On a WebGPU demo with readback, while the canvas resizes the scrolling is very stuttery (without using lots of CPU/GPU) and sometimes leads to 2.5GB+ memory use
Blocks: webgpu-triage

Mayank, are you able to still reproduce this?

Flags: needinfo?(mayankleoboy1)

Ah, nevermind, I can reproduce this on my Windows 11 machine. 😱

Flags: needinfo?(mayankleoboy1)

Even worse...I can reproduce this with dom.webgpu.allow-present-without-readback set to `true.

(In reply to Erich Gubler [:ErichDonGubler] from comment #5)

Even worse...I can reproduce this with dom.webgpu.allow-present-without-readback set to `true.

Same here. I will rename this bug to reflect that the reproduction does not depend on no-readback.

Summary: [WebGPU] On a WebGPU demo with readback, while the canvas resizes the scrolling is very stuttery (without using lots of CPU/GPU) and sometimes leads to 2.5GB+ memory use → [WebGPU] On "ResizeCanvas" webgpu-samples demo, the scrolling is very stuttery (without using lots of CPU/GPU) and leads to 2.5GB+ memory use
Priority: -- → P1

Might be fixed by wgpu#7705?

Status: NEW → RESOLVED
Closed: 3 months ago
Duplicate of bug: 1922992
Resolution: --- → DUPLICATE
Depends on: 1969027
No longer depends on: webgpu-update-wgpu
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: