Open Bug 1749376 (wr-refresh-rate) Opened 3 years ago Updated 4 months ago

[meta] [project] Fix WebRender issues with high refresh rate

Categories

(Core :: Graphics: WebRender, defect)

defect

Tracking

()

People

(Reporter: kvark, Unassigned)

References

(Depends on 13 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

No description provided.
Severity: N/A → S3
Type: task → defect
Keywords: meta
Summary: WebRender issues with high refresh rate → [meta] WebRender issues with high refresh rate

Marking for gfx-triage for awareness on the next call

Blocks: gfx-triage
No longer blocks: 1084070, 1638709, 1713296, 1748800
Depends on: 1738851
No longer blocks: gfx-triage
Depends on: 1749647
Depends on: 1820370
Depends on: 1824971
Depends on: 1747717
Depends on: 1788525
Depends on: 1673072
Depends on: 1698197
Depends on: 1828683
Depends on: 1847040
Depends on: 1875937
Blocks: wr-projects
Summary: [meta] WebRender issues with high refresh rate → [meta] [project] Fix WebRender issues with high refresh rate
Rank: 2
Severity: S3 → S2

For anyone curious what this meta bug is really about, there are a few kinds of bug tracked here:

  • Jank with a video playing on high refresh rate displays
    • The video itself suffers jank when playing a video at 60fps on a 144hz display for example, where we're missing vsync targets repeatedly, hitting pending frame limits in the video decode, and sporadically taking >100ms to draw a frame, spinning on a lock.
    • Autoscrolling while playing a 4K60 video frequently has jank on YouTube, which is probably the same issue.
  • Compositor artifacting
Depends on: 1824916

Regarding the compositor artifacting, those bugs appear to be fixed by https://support.microsoft.com/en-us/topic/may-29-2024-kb5037853-os-builds-22621-3672-and-22631-3672-preview-dcf14fd8-84d6-4234-9d5b-784c319cd7cf (Windows 11 22H2 or later) and https://support.microsoft.com/en-us/topic/june-25-2024-kb5039299-os-build-19045-4598-preview-d4e3e815-fdd8-465e-8144-42afa165efed (Windows 10 22H2, which is the final version), we'll need to confirm with the reporters of the individual bugs.

You need to log in before you can comment on or make changes to this bug.