Closed Bug 254833 Opened 22 years ago Closed 20 years ago

firefox (0.8 -> 0.92) hang on startup after hours of system-idle

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: martin, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7) Gecko/20040707 Firefox/0.9.2 After hours of idle time (about 8-12) firefox is started as first application and nothing happens. Reproducible: Sometimes Steps to Reproduce: 1. do not turn of your computer 2. come back home after x-hours and run firefox as first application 3. usually not more needed Actual Results: The taskmanager reports firefox is running as process (not as application), consuming 1,4MB main-memory. First the explorer hangs up, then (when started) any other application, too. Only a restart is possible using the task-manager (runs in several instances), trying to load another user-profile causes a complete system hang up. I´m using firefox since v0.8, first the english one, then the german, i updated to the english 0.92 and to the german one. I got this "bug" on two complete different systems ONLY when they were running 24h/day. Expected Results: Firefox should start as expected, but just didn´t. The application-logs just reports "firefox cannot be started, DLL initialising failed". Dr.Watson dies with any other application and reports nothing, in fact no monitoring software we tried reports anything. The problem was detected on two complete different systems using W2K build 2195 Sp4 ONLY when running 24h/day, 7day/week. In fact we checked this on 28 other systems NOT running 24h/day and we never got this error. The reprodrucity-rate of this "bug" should be more than 50%. It´s a nice one, we are working on it about 6 months.
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.