Created attachment 899096 [details] prefs.js Description of problem: One folder of an IMAP account, though it doesn't receive any new email (filter and mailing list subscription both disabled), is constantly growing in size on the disk. For instance, after a few days it had grown to 4.6 GB today, while its actual size is 40 MB (you read well, more than 100 times smaller). A temporary fix is to use the "Repair Folder" function of the "Properties" menu enabled by a right click on the directory name from Thunderbird. Version-Release number of selected component (if applicable): thunderbird.x86_64 24.5.0-1.fc20 NB : I already noticed it a few (sub)versions ago, it's been at least a few months. How reproducible: I noticed it only for one folder of one account, though I have many and several accounts. Additional info: The folder has 754 unread emails, 24 of which are marked as new (with a sun) although being almost 2 months old, and 6 read emails.
Does this happen after you trimed/fixed the foldr size, and then started thunderbird in safe??
A comment before answering your question : two days ago I marked all emails of this folder as read, then archived most of them. Today I did the "Repair Folder" trick, and a few things happened. First, all archived emails were back. Second, all emails were marked as unread again. Finally, though the "Folder Properties" window show a folder size of 40 MB, when I click on "Repair Folder" the size on disk decreases only to 300 MB, and during the process of repairing it grows until 341 MB (while before the "Repair Folder" function worked properly and the size on disk went to 40 MB as it should). Now I'll try the safe mode, I'll report about it later.
I just started in safe mode, and it canceled changes mentioned in the last comment. That is, archived emails are archived again and read emails are marked as read again. Size on disk is 310 MB, which is still much more than the 6 MB it should according to "Folder Properties" (I mentioned 40 MB above, it was before the archiving). Let's wait a few days and see if it increases.
Just noticed the following error while running thunderbird from a terminal (I should've try that before) : 2014-08-06 22:24:30 autosyncActivities ERROR OnDownloadError: [name of problematic folder] of [relevant account]
For the moment the size on disk has not increased. However : when I select the problematic folder, all emails are marked as read and archived emails don't appear, but every once in a while archived emails are downloaded and all emails marked as unread again. NB : I'm still in safe mode.
Forget about the 310 MB, I was looking at the wrong file — the right file is indeed 6 MB on disk. It grew to 29 MB this afternoon, so the issue is still present in safe mode.
Confirmed : - 6 MB at 17:19 ; - 12 MB at 21:58 ; - 17 MB at 23:43.
- 23 MB at ?:?? ; - 28 MB at 9:47 ; - 34 MB at 13:22. I noticed that the size increases each time I do the action described in comment 5. That is : I wait for archived emails to be "recovered" and marked as unread, then I open the folder, archived emails disappear, remaining emails are marked as read and downloaded again, and once they've been downloaded the size on disk has increased.
Does this happen with a newer version 31? The problem folder is not an Inbox? Is the problem folder set to check for new mail in folder properties?
(In reply to Wayne Mery from comment #9) > Does this happen with a newer version 31? Not tested yet, I'll try to have a look soon. > The problem folder is not an Inbox? No. > Is the problem folder set to check for new mail in folder properties? No.
(In reply to Wayne Mery from comment #9) > Does this happen with a newer version 31? Yes, it happens with 31.1.0.
Skippy, Is this happening for a gmail account?
(In reply to Wayne Mery (:wsmwk) from comment #12) > Skippy, Is this happening for a gmail account? No, it is a Free (French ISP) account.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.