Threads: unread message count way off: changed from near zero to over 400; increments correctly

RESOLVED INCOMPLETE

Status

Thunderbird
Mail Window Front End
RESOLVED INCOMPLETE
12 years ago
10 years ago

People

(Reporter: Ben Helvensteijn, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: closeme 2008-09-18)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 Netscape/7.1

From one front page check to the next (some 30 minutes in between) the count of unread messages in two main threads went from: 1) near zero to over 400;  2) from around two hundred to over 600.
Since then incremental changes in counts seem to track newly arrived messages correctly, but the high count seems to slow down the initial checks to get going when switching to see the top pages of the threads.
The only coincident odd thing I found was a "commercial message" that got through the spam check that was dated 1969 (!).  Hours went by before I noticed that one and deleted it.  I did not open that message and I also emptied the trashcan.  No difference in response between before- and after deletion and quitting and opening the application again.

Reproducible: Didn't try




The bug happened without any clear cause.  There only was the coincidence of the arrival of unwanted spam, but I am not certain that the Spam had arrived at nearly the same time.
QA Contact: front-end

Updated

10 years ago
Blocks: 438257

Updated

10 years ago
Assignee: mscott → nobody
Reporter, does this issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life, and the latest supported 2.0.0.x is 2.0.0.16)
Whiteboard: closeme 2008-09-18
RESO INCO per lack of response to last comment. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.