150869 - Checking for new messages stops on first empty message

Status: VERIFIED DUPLICATE of bug 103012

(MailNews Core :: Networking: NNTP, defect)

Description

[Gert Kello]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020530
BuildID:    2002053012

When I open the newsgroup account node by clickin the "+" sign, checking for the
new messages starts. But it stops as soon as it encounters first group that has
zero messages in it. Such groups are (for example) in the server
newsgroups.borland.com:
borland.public.announce
borland.public.delphi.announce

Also, I encountered a freeze (99% CPU usage by mozilla) when I opened the
newsgroup node, closed it and opened again - I was using modern theme. But can't
reproduce.



Reproducible: Always

Steps to Reproduce:
1. Add a newsgroup account for newsgroups.borland.com 
2. subscribe to some newsgroups:
borland.public.announce 
borland.public.community (or some other)
borland.public.delphi.announce 
borland.public.delphi.objectpascal
optionally some more
3. close and open the newsgroup account node on the left. No group gets message
count updated.
4. unsubscribe from b.p.announce
5. close and open the node again - borland.public.community get a message count,
others don't.
6. unsubscribe from borland.public.delphi.announce 
7. Close and open the news account node - all groups get the message count updated.

Comment 1

[Gert Kello]

Seems to be a variance of the bug 96415

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

Gert, are you using Leafnode, then?

Comment 3

[Gert Kello]

No, seems that not:

telnet newsgroups.borland.com nntp
Trying 207.105.83.65...
Connected to newsgroups.borland.com.
Escape character is '^]'.
200 dnews DNEWS S2, posting OK 207.105.83.65

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

*** This bug has been marked as a duplicate of 103012 ***

Comment 5

[[e-mail] (gone - use [e-mail] instead)]

verified dup.  we've had reports that this fixed the problem in bug 103012. 
please file a new bug if that hasn't fixed it for you.