Closed
Bug 984931
Opened 12 years ago
Closed 8 years ago
Un-collapsing the profile tree in Cleopatra is very slow
Categories
(Core :: Gecko Profiler, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: smaug, Unassigned)
References
Details
I'm trying to look at http://people.mozilla.org/~bgirard/cleopatra/#report=8e78388aa31ba35b58dec7ecba48ca70af22d59e
Un-collapsing the root has so far taken about 10mins.
We had similar/same issues last autumn, but the time was spent in different place,
since bug 928403 helped quite a bit.
Based on (Zoom) profile Cleopatra triggers _tons_ of restyling, and all the nth child etc
stuff need to be recalculated.
This could be bad css in Cleopatra or some missing optimization in Gecko.
| Reporter | ||
Comment 1•12 years ago
|
||
Oh, and now that the tree is un-collapsed, scrolling it is slow, since tons of restyling is triggered again.
| Reporter | ||
Comment 2•12 years ago
|
||
(Looks like Cleopatra works on Chrome too, and it is slow there too)
Comment 3•12 years ago
|
||
I have a patch somewhere that only creates DOM nodes for those lines that we show (and a bit of buffer around them) which completely removes that performance bottleneck. I should get them landed.
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•