179801 - Missing Usenet Messages (Caused by multiple 3 panes?)

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[(not reading, please use [e-mail] instead)]

from news://news.mozilla.org:119/[e-mail]

>> I've noticed missing posts in all views (Threaded, or not). The posts
>> are on the server, and I can see them with Netscape 4.79 and XNews
>> just fine.  Several times I've noticed I'm missing 2 or more posts in
>> the same thread; usually the first posts of a thread.  I have no
>> filters in use.
>>
>> It seems to be getting worse as I download more articles.  Some sort
>> of indexing problem?
> 
> 
> I may have relized how this is happening. In Mozilla 1.1 (Win) it's
> easy to 'accidently' open up another mail/news window.  If I open up
> a second window while the first is still active, and my news account
> and groups tab is expanded, the news client goes out and queries
> the server for newer message counts for each group.  If I then close
> that window, the counts have been updated in the .newsrc, but the
> old (original) window does not reflect this and there is no way to
> retreive headers/message counts again since the first news-window
> now thinks there's less messages than there really would have been
> had the second window not already retreived the message counts.
> Hence, missing posts.
> 
> This could potentially be a problem with POP mail accounts also
> (Unless messages are automatically downloaded...which is usually the
> case I beleive <shrug>?)
> 
> Anybody familiar with the internals enough to think this could be
> the problem?  Is there any way to keep a second mail/news client
> window from being spawned, and only have one active at any given time
> as in Netscape 4.xx? (There was a way to open 2 news clients in
> Netscape, but it was a roundabout way, plus the newsgroup tabs were
> always minimized (shrunk) until you explicitly expanded the server/group
> tab.

Comment 1

[David :Bienvenu]

yikes, yeah, this could be a problem. It's not obvious why opening a second
window could cause this, though - we do record a highwater mark of messages
we've fetched, but we then fetch all the headers between our previous highwater
mark and the current highwater mark, so what we do after that shouldn't affect
the headers downloaded. If the download were interrupted/stopped, I could
imagine that we might have problems if we aren't careful adjusting the highwater
mark.

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420