Closed Bug 1421611 Opened 2 years ago Closed Last year performs badly and renders wrong


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






(Reporter: jrmuizel, Unassigned)


(Blocks 2 open bugs)


(Whiteboard: [wr-reserve])

No description provided.
Whiteboard: [wr-mvp] [triage]
Priority: -- → P3
Whiteboard: [wr-mvp] [triage] → [wr-mvp] [triage][wr-reserve-candidate]
Whiteboard: [wr-mvp] [triage][wr-reserve-candidate] → [wr-reserve]
So many codepen testcases are not working anymore because their SCSS seems broken. I should try to inform them.
Flags: needinfo?(jan)
Broken test case. Plead for INCOMPLETE.
Flags: needinfo?(jan)
Looks like codepen's SCSS compiler has a bug. Here's a fork of the testcase that works:
(I compiled the SCSS using and pasted the result as raw CSS.)

All the time is being spent in the content thread and in the render backend. The renderer thread is not very busy and is capable of sending a lot more frames to GL than it does.
All the animations on this page are OMTA animations. Once we have async scene processing for OMTA, the render backend's slowness will not affect the frame rate. And once we throttle the animation on the content side (bug 1419851), the render backend will not get distracted by unnecessary new display lists.

The render backend spends 45% of its time in memory allocation and deallocation.
Depends on: 1419851
So, bug 1419851 has been fixed, it might be worth taking a new profile on the latest nightly? is a new profile. But on my macOS nightly with WR enabled it seems to perform better than on beta with WR disabled. So maybe we can just close this as fixed.
That's good to know. :)
Forgot to leave more comments.

In the profile in comment 6, I noticed one thing we can optimize which is related to animations, I've filed bug 1463605 for that.

Closed: Last year
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.