455596 - Strange Firefox behavior after some web page has been opened in a background tab

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Vincent Lefevre]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-GB; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-GB; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1

When the page http://www.basango.com/index.php?action=breve&id_article=1039149 has been loaded in a background tab (i.e. it is not the tab that is currently displayed), Firefox is slow and behaves strangely (see below).

Reproducible: Always

Steps to Reproduce:
1. Open http://www.basango.com/index.php?action=breve&id_article=1039149 and other tabs. Make sure that the tab that is currently displayed does not correspond to the given URL (otherwise the following problems do not occur).
2. Switch to another application.
3. Click on the Firefox window.
Actual Results:  
* The Firefox window doesn't go to the foreground (if it wasn't already).
* The Firefox menu doesn't appear (one still has the menu of the previous application).
* The mouse wheel has no effect.
* When moving the mouse pointer over a link, the shape of the mouse pointer doesn't change (but the status line is updated as expected, displaying the URL of the link).
* Firefox is slow to respond to events.

Expected Results:  
These problems should not occur.

When the given URL is open, Firefox takes 100% CPU time.

Comment 1

[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 2

[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.