1961380 - feeds.json-*.corrupt in RSS tree

Status: RESOLVED INCOMPLETE

(Thunderbird :: Untriaged, defect)

Description

[macuc]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0

Steps to reproduce:

• Updated TB to 128.9.2esr (64-bit) (Windows 10)
• Open TB, view RSS fee tree list.

Actual results:

The first time I opened TB after the update a new folder appeared in my RSS feed tree view named, "feeds.json-1.corrupt" This folder contains nothing when clicked on. The second time I opened TB, "feeds.json-1.corrupt" was still displayed, and a new folder named, "feeds.json-2.corrupt" appeared under it. The new folder also contains no items. I am now up to "feeds.json-7.corrupt" after opening TB 7 times!

Expected results:

None of this should have happened.

Also, on my Windows 11 install of TB 128.9.2esr (64-bit), I have not observed this happening at all.

Comment 1

[macuc]

Attachment: rss-bug.jpg

Comment 2

[macuc]

I just now realized that none of my RSS feeds have updated since the upgrade to TB 128.9.2esr on Windows 10.

So it looks like I'm going to have to delete all my RSS feeds and add them back again to get around the corruption caused by the upgrade.

Comment 3

[macuc]

• I tried running Repair Folder on several of the RSS feeds. But they did not regain their ability to download messages.
• Existing messages in the folders, including unread messages, display with no problems.
• I tried to delete all the feeds.json-*.corrupt folders from the RSS feeds tree, then closing and re-opening TB. A new folder appeared, but it was not named "feeds.json-1.corrupt" as I expected. Instead, it is named, "feeds.json-9.corrupt" since this is the 9th time I opened TB since updating it to 128.9.2esr.

Comment 4

[macuc]

Attachment: Found in profile Mail\Feeds\ folder

Maybe this will help. I found these two files in the C:\Users[username]\AppData\Roaming\Thunderbird\Profiles[profile]\Mail\Feeds\

Comment 5

[Magnus Melin [:mkmelin]]

Right, for whatever reason your feeds.json file got corrupted. You'll want to grab one from your back-ups if you have any.
Why it got corrupted we'll never know.