Closed Bug 1736871 Opened 3 years ago Closed 11 months ago

[meta] Profiles should contain enough information to understand why compositing happens at 60Hz

Categories

(Core :: Graphics: WebRender, enhancement)

Product:
Core
Component:
Graphics: WebRender
Type:
enhancement

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mstange, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: meta)

Example profile: https://share.firefox.dev/3pqBsDT

When continuous compositing is happening, it can still be hard to find out what's causing it. In many cases it's because we think a CSS animation is running, but it can be hard to trace it to the source.

This is a meta bug for collecting more information for these cases.

Example profile https://share.firefox.dev/3lVphg2 (from bug 1733377 comment 7) with the new markers added in bug 1690619, showing "Render reason ANIMATED_PROPERTY", but we are left wondering which property is animated.

Summary: [meta] Profiles should contain enough informations to understand why compositing happens at 60Hz → [meta] Profiles should contain enough information to understand why compositing happens at 60Hz
Severity: -- → N/A

There are actionnable suggestions in bug 1690619 comment 1.

Depends on: 1757202

I think this happened?

Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.