On 10/31/2009 04:58 PM, Hartmut Figge wrote: > User: > >>One thing I have never been too clear about the newsgroup function on the >>Mozilla suite / Seamonkey - if I have a newsgroup server collapsed in the >>news >>folder pane, then the newsgroup server is NOT accessed UNTIL I either >>highlight >>the news server or open it and highlight one of the newsgroups hosted on the >>server, is that correct? > > Unfortunately not true for at least SM2.0 nightlies of the last months > and now SM2.1. It became obvious with the increase of the load during > the fetch of new postings. Btw, the time frame for this is > > h...@e675 ~ $ fenster 0909240813-0909251108 > 2009-09-23 23:13:00 PDT > 2009-09-25 02:08:00 PDT > > as i had written in <[email protected]> > > At the moment the collapsed state of a newsserver is not honored when > new postings are automatically fetched or at the start of MailNews. All > what matters are the two checkboxes for 'Check for ...' under Server > Settings. > > Well, this is a horrible waste of bandwidth and useless also. If a > newsserver is collapased, why should he care about new postings? > > I had lamented strongly about this issue in dcsm. *g* > > Hartmut
I have 'Check for...' turned off for all news servers, but have grown accustom to the high cpu when checking my gmane.org newsgroups in 2.0 where I have at least 25 subscribed groups. Perhaps I got used to it in testing 2.x pre/nightly/alpha/beta etc. When I first open the server (click the right triangle next to the server name), cpu skyrockets & all things mozilla pause. I can confirm that this does not happen when doing the same from my 1.1.18 (linux & windows). This is a valid issue. But I've not bothered searching for a bug report yet, but would appreciate it if perhaps you know of one already opened? _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
