Closed
Bug 1413763
Opened 7 years ago
Closed 2 years ago
Hidden arrow panels keep trying to composite at 60fps
Categories
(Core :: Graphics: Layers, defect, P3)
Core
Graphics: Layers
Tracking
()
RESOLVED
DUPLICATE
of bug 1742797
Performance Impact | low |
People
(Reporter: mstange, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf, perf:resource-use, power, Whiteboard: [gfx-noted])
Attachments
(1 file)
1.44 KB,
patch
|
Details | Diff | Splinter Review |
Steps to reproduce: 1. Be on Windows, or apply the attached patch on Mac so that arrow panels use a transform animation. 2. Open a tab and go to about:blank. 3. Click the hamburger button in the toolbar so that the panel opens. 4. Click into the content area of the tab so that the browser closes. 5. Start your profiler, wait for a few seconds, and grab a profile. Actual results: There are compositor markers at 60fps even though the browser should have been completely idle. Expected results: No attempted compositing and 0% CPU usage. If you're running a build that has --enable-dump-painting, you can flip the pref layers.dump-host-layers to true and see the browser printing LayerManagerComposite trees at 60fps. I found this bug while investigating bug 1400259.
Reporter | ||
Comment 1•7 years ago
|
||
Example profile: https://perfht.ml/2z7YW4s
Comment 2•7 years ago
|
||
Oh unfortunately this can't reproduce on Linux? How do we hide the panel? If we do hide by setting visiblity:hidden, the transform animation keep running. I've tried to fix it in bug 1237454.
Flags: needinfo?(mdeboer)
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: [gfx-noted]
Comment 3•7 years ago
|
||
So the 'panel' we're talking about is the 'popup' binding, but the element in use is called '<panel type="arrow"/>'. This confuses me all the friggin' time, so I thought I'd mention it ;-) Regardless, the way we hide popups is by calling `panel.hidePopup()`, which is implemented in layout/xul/PopupBoxObject.cpp and friends. This, I believe, ends up calling `nsView::SetVisibility(nsViewVisibility_kHide)`. How that gets processed, I don't know exactly. But I hope this gives you enough hints to see how deep this rabbit hole goes?
Flags: needinfo?(mdeboer)
Updated•6 years ago
|
Comment 5•6 years ago
|
||
Seems like it's worth looking into soon, especially considering the update dialog which is an arrow panel that pops up on its own and doesn't go away unless it's explicitly dismissed.
Whiteboard: [gfx-noted][fxperf] → [gfx-noted][fxperf:p2]
Comment 6•5 years ago
|
||
Doesn't really feel like an fxperf bug; maybe something for quantum flow? I wonder if wasting CPU on this can slow down page load.
Whiteboard: [gfx-noted][fxperf:p2] → [gfx-noted][qf]
Updated•5 years ago
|
Whiteboard: [gfx-noted][qf] → [gfx-noted][qf:p3:resource]
Updated•3 years ago
|
Blocks: power-usage
Reporter | ||
Comment 7•2 years ago
|
||
This was re-filed as bug 1742797. Let's move the conversation there.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
Updated•2 years ago
|
Severity: normal → --
status-firefox58:
affected → ---
Updated•2 years ago
|
Performance Impact: --- → P3
Keywords: perf:resource-use
Whiteboard: [gfx-noted][qf:p3:resource] → [gfx-noted]
You need to log in
before you can comment on or make changes to this bug.
Description
•