716445 - Slow menu dropdown - regression vs. 3.6

Status: RESOLVED WORKSFORME

(Core :: General, defect)

Description

[Randell Jesup [:jesup] (needinfo me)]

Spun off from a report in bug 490122, since this report appears to document a different issue than that bug (menu (and other) graphical slowness, not periodic stalls.)


Original report:
[e-mail] (New to Bugzilla) 2012-01-07 20:54:36 PST

I have the same problems that David.P does.  In my experience GC is a problem too, but there is no question that FF4 is far slower graphically (on my hardware) than FF3.6.  As soon as I tried FF4 for the first time I noticed it.

Like David, I find everything about the way pages are displayed slower (eg. scrolling).  For example, an easy way I found to compare performance is to go to http://www.mozilla.org/en-US/firefox/features/ and run my mouse back and forth between 'Desktop' and 'About' on the menu's at the top.  

In FF3.6 my CPU hovers 20-40%; all the menus dropdown on queue.  

In FF10 this PINS my CPU; the menus only dropdown if I keep my mouse hovering on one of the items for about half a second.

I've tested this on clean profiles, no extensions, one tab.  Disabling hardware acceleration in FF and in XP makes no difference.  I also tried disabling hyper-threading, write combining and gfx.canvas.azure.

Windows XP SP3
3.00 GHz Pentium 4
256MB NVIDIA GeForce 6200 (EVGA)

Comment 1

[Boris Zbarsky [:bzbarsky]]

A minimized testcase would be useful.  Are the menus using CSS features that 3.6 doesn't support, for example?

Comment 2

[Wayne Mery (:wsmwk)]

yamiravko...

(In reply to Boris Zbarsky [:bz] from comment #1)
> A minimized testcase would be useful.  Are the menus using CSS features that
> 3.6 doesn't support, for example?

Comment 3

[tyaremco]

I am formally yamiravko.

I don't have this machine to test on anymore.  Someone else with similar hardware will have to look into it.

This was the page in question from the OP, although something about archive.org's copy results in the menus not disappearing on mouseout in FF28.
https://web.archive.org/web/20120107034715/https://www.mozilla.org/en-US/firefox/features/

Comment 4

[yamiravko]

No longer an issue.  Bug can be closed.