289142 - Firefox version 1.0.2 - firefox.exe process hangs on exit

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Bisser Dobrev]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

This has been a problem since my upgrade to 1.0.2. I have reproduced it on two 
machines - one XP SP1 and one XP SP2 to be sure. Both worked great with 1.0.1.

It seems that the first time Firefox is started it works fine, until you try 
to open a new instance and:

1. It never happens
2. After you exit the first instance, the process is still there.
3. Killing the process and trying to start another instance, makes Firefox 
start and acts like a zombie - it just sits there, no menus or buttons are 
clickable and it does not seem to go to the default home page. 
4. At this point you close it and kill the process second time. Now you can 
open a fresh instance which will work okay (until you try to start a second 
instance)

Also, this issue seems to be related to bug #287538.

Reproducible: Always

Steps to Reproduce:
1. Open Firefox (home page http://www.google.com)
2. When complete, click to open Firefox second time. It will not open. At this 
point after you close the first Firefox window, you will notice that the 
process does not end as expected.
3. Killing the process and restarting Firefox does not work from the first, 
but from the second time.
Actual Results:  
Second window does not open.

Expected Results:  
Second window should open as expected.

The following extensions are installed and up to date:

1. googlebar 0.9.0.30
2. User Agent Switcher 0.6.4
3. Minimize to Tray 0.0.1.20050212
4. Web Developer 0.9.3

Comment 1

[Gabriel Chadwick]

this wfm using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2)
Gecko/20050404 Firefox/1.0+

Comment 2

[Colin S]

WFM also, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6)
Gecko/20050317 Firefox/1.0.2

You should try with a fresh profile to see if that fixes the problem.

Comment 3

[Bisser Dobrev]

Is that it? Thanks for the suggestion, but I don't believe that is even close 
to RESOLVED. 

1. One of the computers has been re-installed a month ago. The other has not 
been touched for more than 6 months. 
2. Why would I have to even think of redoing my profiles when everything else 
works great with those profiles?
3. I'm sure that it probably WFY, but it does not WFM. From a QA stand point, 
I would expect some more interest from the developers on an issue like this. 
Many of the bugs are machine specific and should be regarded the same way as 
the more common ones. 
4. I am seriously considering other browsers, because I really need a browser 
that works. Version 1.0.2 presented too many problems, and instead of getting 
better it seems to get worse. 

Comment 4

[Gabriel Chadwick]

This bug can not be confimed because we have no clue of wich component of
firefox is responsible of this. If you can give more information on how to
reproduce. A testcase or a talckback id would really help. You should also test
this with the lastest trunk in order to see if it repeats. You should test this
with a new profile to narrow the problem down.