510804 - Firefox "locks up" when more than one tab is opened.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[imjrk]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Q312461; .NET CLR 2.0.50727)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2

When I open a second tab within seconds my CPU usage goes to 100% and everything goes to a crawl.  When I go to "Task Manager" Firefox shows as "not responding"  I need to "end task" to close Firefox, so I get control back.  This is not happening with IE8, I can have as many tabs as I want open.  This problem actually began when I upgraded to ver.3.  It has gotten unbearable with 3.5.  I HATE IE, but I have no choice.  I have been using Firefox since Netscape sold out.

Reproducible: Always

Steps to Reproduce:
1.Open multiple tabs in Firefox
2.CPU usage goes to 100% and does not fall.
3.
Actual Results:  
Open Firefox, open a second tab, CPU usage goes to 100%.

Expected Results:  
Had to "end task" using task manager, Firefox not responding.

Additional tabs should not run the CPU from 10%, or so, to 100% and stay there.

Comment 1

[u348128]

Can you give the sites you open? There are many people that have dozens of tabs open without any problem. But some sites may give problems on Firefox.

Lucas

Comment 2

[Matthias Versen [:Matti]]

Does it work in the Firefox safemode ?
http://support.mozilla.com/en-US/kb/Safe+Mode

Comment 3

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 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.