Closed Bug 1753140 Opened 3 years ago Closed 2 months ago

Background animation is not smooth on sub.v1.mk

Categories

(Core :: Graphics: Canvas2D, defect)

Firefox 98
Desktop
Windows 10
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox98 --- affected

People

(Reporter: ksenia, Unassigned)

References

(Depends on 1 open bug, )

Details

​​### Basic information
This was originally reported in https://github.com/webcompat/web-bugs/issues/98601

Steps to Reproduce:
Visit https://sub.v1.mk/ in Firefox Nightly 98.0a1 (2022-01-26) and observe the background
(the canvas element in the background is only visible when Firefox is in light theme mode)

Expected Results:
Animation is smooth

Actual Results:
Animation is not smooth


Performance recording (profile)

Profile URL: https://share.firefox.dev/35r1pLt

System configuration:

OS version: Windows 10 Pro with webrender enabled

https://share.firefox.dev/3ukjFka
Profile looks Canvas-y

Component: Performance → Canvas: 2D

The severity field is not set for this bug.
:lsalzman, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(lsalzman)

Bob, ideas here? I am not seeing anything in the profile that jumps out at me other than some keyed mutex waits on the canvas, but I am having trouble identifying anything in the profile tracks that would look like it is actually doing any kind of heavy intermittent processing at all.

Severity: -- → S4
Flags: needinfo?(lsalzman) → needinfo?(bobowencode)

(In reply to Lee Salzman [:lsalzman] from comment #3)

Bob, ideas here? I am not seeing anything in the profile that jumps out at me other than some keyed mutex waits on the canvas, but I am having trouble identifying anything in the profile tracks that would look like it is actually doing any kind of heavy intermittent processing at all.

It's all happening during DrawTargetD2D1::FlushInternal and those mutex waits are just the content process waiting for the GPU canvas thread to catch up.
If I turn off remote canvas I get basically the same thing with the content process main thread waiting on the flushes.

In both cases about 30% seems to be in NtFreeVirtualMemory from ~TransformableTessellationStore, which seems a bit crazy.

Flags: needinfo?(bobowencode)
Webcompat Priority: --- → ?

Seems to be a minor perf issue, not a webcompat issue.

Webcompat Priority: ? → ---

This is fixed by gpu-canvas: https://share.firefox.dev/4cfcNH9
Still repros with d2d-canvas: https://share.firefox.dev/4dtWYxg

Depends on: gpu-canvas

Latest profile: https://share.firefox.dev/3EvOh9y
Should this bug be closed as fixed?

Flags: needinfo?(kberezina)

With no response from reporter, I'm going to mark this as fixed due to comment 6 and comment 7.

Status: NEW → RESOLVED
Closed: 2 months ago
Flags: needinfo?(kberezina)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.