RESOLVED WORKSFORME

Status

()

Core
Graphics
RESOLVED WORKSFORME
2 years ago
2 years ago

People

(Reporter: marco, Unassigned)

Tracking

({perf})

46 Branch
x86_64
Linux
Points:
---

Firefox Tracking Flags

(firefox46 affected)

Details

(Whiteboard: gfx-noted)

Attachments

(1 attachment)

717.48 KB, application/x-7z-compressed
Details
(Reporter)

Description

2 years ago
The animation in "tag cloud" on the right causes scrolling to be really slow.
(Reporter)

Comment 1

2 years ago
Created attachment 8702926 [details]
profile.7z
Flags: needinfo?(mchang)
Keywords: perf
Whiteboard: gfx-noted
This profile seems to be in a .bin format? What kind of profiler were you using with the attached profile? Thanks!
Flags: needinfo?(mchang) → needinfo?(mcastelluccio)
(Reporter)

Comment 3

2 years ago
The Gecko Profiler add-on.
Flags: needinfo?(mcastelluccio)
From the profiles, I see super long 500+ms times to do XRender::Sync, _XSEND and XUnlockDisplay. I know we're planning to reduce our dependence on XRender, which should help this test case.
Depends on: 1241832
(Reporter)

Comment 5

2 years ago
It's still slow, I can grab another profile (although bug 1241832 caused bug 1247935, so I don't know if it'll stick).
(Reporter)

Comment 6

2 years ago
This is now fixed (both with gfx.xrender.enabled set to true or false), I wonder if this was fixed by the same fix for bug 1247935.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
(In reply to Marco Castelluccio [:marco] from comment #6)
> This is now fixed (both with gfx.xrender.enabled set to true or false), I
> wonder if this was fixed by the same fix for bug 1247935.

That makes sense, yes. As Mason noted, a lot of the profile was spent in XSync waiting for stuff to be drawn. So if there was somehow contention for the connection to the X display, the changes I made in bug 1247935 would massively reduce that contention, since it no longer uses the XSync mechanism at all.
Depends on: 1263222
No longer depends on: 1263222
You need to log in before you can comment on or make changes to this bug.