279692 - sporadic hanging after sp2 installation

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[David Ziegler]

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.5) Gecko/20041107 Firefox/1.0

On a number of websites (it seems to be just about anything I visit), Firefox 
sporadically stops responding completely.  It's not consistent when it 
happens -- sometimes it's mousing over a link, sometimes clicking a link, 
sometimes scrolling.  Every time it happens, it just stops responding 
completely.  CPU usage remains at 0%.

It's defintely related to service pack 2.  It worked fine before SP2 
installation (this is a fresh Windows installation).  Just to be sure, I 
reformatted the drive, installed all updates but SP2, and it worked great 
(consistently).  After updating, the problem returned.  Only Firefox and 
Windows are installed.

Reproducible: Sometimes

Steps to Reproduce:
1. Go to a website
2. Do something
3. It hangs
Actual Results:  
Firefox stops responding.  It usually returns within 10 seconds or so.

Expected Results:  
Continued responding.

This is a new, fast computer (so it's not a hardware problem).  3.0 GHz, 1 GB 
ram.  It's also Firefox-specific.  I have not had any problems with IE or 
other software.  Additionally, I've tried a number of tweaks to see if it 
solves the problem.  I saw someone suggested turning off DEP, it had no 
effect.  I've modified TCP/IP settings to see if it's network problems, no 
change.  As much as I don't want to use IE, Firefox has become unusable at 
most times.

Unfortunately, I don't have a talkback crash ID to provide -- it doesn't 
crash, it just hangs.  I have killed it with task manager, but I don't receive 
a talkback crash ID to enter.  If someone knows how to generate one, I would 
be happy to do so.  If there is any other information I can provide that would 
be useful, I would be more than happy to do so -- I use Firefox on Linux and 
love it.  Thanks for the assistance!

Comment 1

[Colin Peart]

Me Too.
I have this exact same problem on a fresh install of WinXP Pro SP2 on a 3GHZ 
P4 with 1gig of ram.  Actually, it occurs on two matching computers here in my 
office that I just set up.  Both of them use an MSI TV5200 (nvidia 5200 
chipset, 128mg ram) for video cards, though one of them has a second s3Virge 
video card as well.
I am going to build a copy from source with debug symbols so that I can find 
out where it is hanging -- any suggestions?  I have tried the regular build 
from mozilla.org/firefox and on the moox M3 build, as well as the nightly -- 
same result.

Comment 2

[David Simcha]

Could this be an XP Pro-specific problem?  I use Home Edition and Firefox never
hangs for me on either my Athlon XP 2600+ or my dad's Celeron 2.6, both of which
have XP Home SP2.  

David Ziegler, please inform us as to whether you have XP Home or XP Pro.  Thanks.

Comment 3

[David Ziegler]

It's XP Pro.  It *might* be an XP Pro-specific problem.  That is, I've only 
seen it on XP Pro -- but then again, I've only seen it on one computer. 

Comment 4

[u88484]

I expirence this all the time at college on 5 computers. I think at school its
becuase of the virus scanner. takes at least 30 seconds to open firefox at
college and like 1/2 second to open at my house on much much slower computer.

Comment 5

[Mike Connor [:mconnor]]

minusing, no clear steps to reproduce, "stuff happens randomly" isn't something
we can fix really.  Lots of people are on SP2 without this issue, including my
three XP boxes, so it could be any number of things (drivers, config, etc).

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.