Closed
Bug 790966
Opened 12 years ago
Closed 10 years ago
Multiple repaints more expensive with gfx.content.azure.enabled=true (was: Tab animations slower with gfx.content.azure.enabled=true)
Categories
(Core :: Graphics, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: marco, Unassigned)
References
Details
Enabling Azure for content slows down tab animations.
The weird thing is that FX_TAB_ANIM_CLOSE_MS and FX_TAB_ANIM_OPEN_MS are similar (~300ms with or without the option set). But the animation with the option set to true is noticeably slower (mainly the opacity transition).
Updated•12 years ago
|
Reporter | ||
Comment 1•12 years ago
|
||
I figured out this problem occurs only if browser.newtab.preload=true.
Reporter | ||
Comment 2•12 years ago
|
||
With browser.newtab.preload=true, FX_TAB_ANIM_CLOSE_MS is ~30ms longer with gfx.content.azure.enabled=true than with gfx.content.azure.enabled=false.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•12 years ago
|
||
Isn't the difference between gfx.content.azure.enabled=true and gfx.content.azure.enabled=false worth investigating?
Comment 5•12 years ago
|
||
(In reply to Marco Castelluccio [:marco] from comment #4)
> Isn't the difference between gfx.content.azure.enabled=true and
> gfx.content.azure.enabled=false worth investigating?
Yeah, sorry, I think it might be worth investigating why excessive invalidation is more expensive with Azure enabled.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Reporter | ||
Updated•12 years ago
|
Summary: Tab animations slower with gfx.content.azure.enabled=true → Multiple repaints more expensive with gfx.content.azure.enabled=true (was: Tab animations slower with gfx.content.azure.enabled=true)
Comment 6•12 years ago
|
||
I think this -might- be related to bug 778367. I'm currently debugging an issue with that bug, we can try again after that.
Comment 7•12 years ago
|
||
We should retest on tomorrow's nightly which will have the fix to bug 778367
Comment 8•12 years ago
|
||
(In reply to Bas Schouten (:bas.schouten) from comment #7)
> We should retest on tomorrow's nightly which will have the fix to bug 778367
Marco, can you retest?
Whiteboard: [Snappy]
Comment 9•10 years ago
|
||
Can you still reproduce the issue with latest version with clean new fresh profile without any addons and plugins?
Flags: needinfo?(mar.castelluccio)
Reporter | ||
Comment 10•10 years ago
|
||
The configuration option doesn't seem to exist anymore, so I wouldn't know how to test this.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 10 years ago
Flags: needinfo?(mar.castelluccio)
Resolution: --- → INVALID
Comment 11•10 years ago
|
||
FYI - Auzre is probably forced enabled now.
So if this issue is not present anymore it's good.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•