All users were logged out of Bugzilla on October 13th, 2018
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 Note: my gut feeling is that this is related to bug 77872 and perhaps 84042 and 221479. It has been present since Netscape 4.x at least Component: News When I subscribe to a news group de-novo the entire user interface of Mozilla: News, e-mail, and the web browser freeze entirely and the Windows 2000 CPU time meter goes to 100%. This is bug 77872. It only occurs in groups with lots (minimum number not verified, but 25000 will do it) This freeze lasts minutes. Eventually the freeze ends and the news items appear, and I can read them. However, if I click on the little icon that resorts them in date order another very long, though not quite as long, still minutes, freeze of identical nature occurs. If I then resort by thread, and then again sort by date, it does NOT reoccur, important to note. The other resorts cause freezes of the order of 1 second, not minutes. Reproducible: Always Steps to Reproduce: 1.Subscribe to a brand new Newsgroup that contains 25,000 or more messages 2.Wait until the messages are loaded 3.click on Date bar to resort by date Actual Results: All of Mozilla, news, e-mail, and browser, has complete user interface freeze. Mozilla goes to 100% of CPU time. Other programs, including Internet Explorer and stand alone network programs operate normally, reducing the 100% by whaever they need. Expected Results: only News and e-mail freeze, and even they allow hitting a "Stop" button to unfreeze Notes: 600 Mhz Pentium III with 512 megabytes memory; no large disk activity noted during sort, I have not tried the "sort" after loading a new Newsgroup and then shutting off the computer to flush disk cache.
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.