291404 - New Win2K patches are causing system lockup when FF is used.

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[William M. Moss]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

I installed the latest MS patches (KB890859, KB893086, KB893066). Once
installed, the system would lock up whenever Firefox was used to access the
Inet. The system lockup seems to be memory related, but the lockup occurs
inconsistently; that is, always when I access a new URL but not necessarily the
same URL or after the same amount of time. Removal of all the patches cured the
problem. Neither the boot log, DRWATSON or any other of the Win2K trace tools
has any useful information. I intend to put the patches, one at a time, on a
spare machine and see what happens. System hardware, which may be effecting
this, is an AMD Athlon @ 1.1 MHz w/ 768 MB of RAM, an Adaptec 29160 controller,
Creative Labs 24 bit live sound card, DFI system board, D-Link NIC and an ATI
Rage AGP-4 video card.

Reproducible: Always

Steps to Reproduce:
1.Open FF
2.Log into my ISP (Verizon DSL) from the router.
3.Access a number of URL's

Actual Results:  
System locks and will not respond to an ICMP (ping) from another machine on the
LAN (inside the router).

Expected Results:  
Run as normal. I do not think this is necessarily a FF bug, but a case of MS
doing its thing without regard to the rest of the world.

To reiterate, removal of all the Knowledge Base patches restored normal operation.

Comment 1

[OstGote!]

KB893066 has regressions on W2K, see http://support.microsoft.com/kb/890345/.
Please check if this applies for you and report it here.

Comment 2

[Frank Wein [:mcsmurf]]

(In reply to comment #1)
> KB893066 has regressions on W2K, see http://support.microsoft.com/kb/890345/.
> Please check if this applies for you and report it here.

Reporter: Can you answer that question?

Comment 3

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

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