Closed Bug 715300 Opened 13 years ago Closed 12 years ago

If a rss feed folder has more than 4k items thunderbird does not register "read" after closing

Categories

(MailNews Core :: Feed Reader, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: 133794m3r, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0.1) Gecko/20100101 Firefox/8.0.1
Build ID: 20111120135848

Steps to reproduce:

I have a bunch of reddit rss feeds on thunderbird, in total they number ~5k entries at the moment. Ever since they reached more than 4k, it does not register an article as read. When I go back to it the next day, I see things that I've already looked at as "new". 


Actual results:

the feed resets for some odd reason after closing down thunderbird.


Expected results:

It should be able to handle it.
OK i have another one that is at 8k in total, but it's from ~20 or so rss feeds. It seems to be happening because it's only 3 rss feeds that have that many entries.
(In reply to 133794m3r from comment #1)
Just after you mark an article as read, is there any error appearing in the error console?
Component: General → Feed Reader
Product: Thunderbird → MailNews Core
QA Contact: general → feed.reader
Does rebuilding the folder fixes the issue ?
First off, how do i rebuild the folder? Secondly I didn't look, after reporting this bug I decided to say "screw it" and deleted ~7k items. I'll wait for it to be rebuilt since it should go rather quickly(it's feeds from various reddits).
Or my other folder that does /., hacker news, engadget, ars,bgr, ... should get there first. Currently at 6,192 messages.
Right-click on the folder -> Properties -> Repair folder.
the number of messages is unlikely to be relevant, and repairing the folder is the solution.  starting in Tb13, feed folders are auto repaired when necessary on a new messages operation.  please open an new bug if this happens in Tb13 or later.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.