leaving browser unattended for 24hrs causes entire machine to lock up and absorb 100% processor




15 years ago
14 years ago


(Reporter: MrFadedGlory, Assigned: bugzilla)


Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2
Build Identifier: Firefox/0.9.2

on a Win2K platform (IBM A31, Intel pentium p4 chip, 30GB HDD, 512mb RAM)
leaving FireFox 0.9.2 unattended over night while connected to the web (ADSL
512kbps connection speed) results in FireFox absorbing all system resources
particularly processor (using task manager it is obvious that processor is at
100% and memory usage is up at 350+MB).  System cannot be shut down normally and
power supply must be interrupted to effect a reset.

I am running a Zone Labs fire wall, generally I have Mozilla Mail 1.7, xChat
2.0.8. MSN Messenger v6.1 (6.1.0211) and Microsoft Office Outlook 2003
(11.5608.5606) running concurrently with FireFox.  The problem only occurs when
FireFox is running however.  When it is not running and the others are all up,
things are fine.

This problem occurred when i was using Moz 1.4 - 1.7 release candidates, but
went away when the actual release of each of these came out.

Reproducible: Always
Steps to Reproduce:
1.  Start FireFox 0.9.2 
2.  Leave over night
3.  Experience problems

Actual Results:  
the entire machine freezes up, the screem will refresh within 30 minutes to
reveal the system manager showing 100% processor usage and memory spiked over 350mb+

Expected Results:  
not frozen my machine
Reporter, does this ever occured again with a current build? I've never seen
such an issue except on site with flash where it happens immediately.
Summary: leaving browser unattended for 24hrs causes entire machine to lock up and absorb 100% processor → leaving browser unattended for 24hrs causes entire machine to lock up and absorb 100% processor
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/
No respone over a long time => INVALID. Feel free to reopen if it's still an
issue for you and reproducable with current builds.
Last Resolved: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.