460345 - 100% CPU usage by the xserver process *only* when main throbber spins

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[mozstuff]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081016 Minefield/3.1b2pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081016 Minefield/3.1b2pre

When the current tab is being updated (ie, the main throbber on the menu bar is being updated) the xserver cpu usage will go to 100%. This does not happen if the page is loaded in a different tab while the current tab is idle/blank (ie no main throbber updates)

Easiest way to reproduce is cause the proxy authentication dialog to appear. The main throbber will spin and the xorg CPU will go to 100% everytime. Completely reproducible. This problem has been there for some time, but I have just now narrowed it down to this. I proeviously thought it was cause by certain web sites, but it appears to be something more basic to firefox.

Reproducible: Always

Steps to Reproduce:
1.Configure an authenticating proxy
2.Attempt to use said proxy
3.CPU will spike immediately when authentication dialog appears

-or-

pick a website with significant load time. If loaded in current tab you get a spike, if loaded in background, no spike. Spike occurs only when main throbber is being updated.

Actual Results:  
Xserver cpu goes 100% and all interactive response goes to ****.

Expected Results:  
Xserver cpu use should not peg at 100%. It should behave the same as it does when loading into a background tab.

Comment 1

[mozstuff]

removing the main throbber fixes the problem completely. Throbbers on tabs do not seem to be a problem, just the main one. It appears from my screen that firefox is constantly updating the menubar and toolbars when the main throbber spins.

Comment 2

[Tyler Downer [He/Him]]

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

Comment 3

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.