[Users] [Bug 4602] New: Slow folder opening due to cache rebuild
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Sat Jun 4 23:42:32 CET 2022
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4602
Bug ID: 4602
Summary: Slow folder opening due to cache rebuild
Product: Claws Mail (GTK 2)
Version: 3.17.8
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Folders/IMAP
Assignee: users at lists.claws-mail.org
Reporter: jerome at jolimont.fr
Hi.
I'm using claws-mail with IMAP.
While most folders open instantly, some folders take ages to open: INBOX, Spam
and some random subfolder of another folder seem to be the only impacted ones.
When in debug mode, I get those in the logs:
imap.c:1584:trying to fetch cached
/home/jerome/.claws-mail/imapcache/domain/address/Folder/5357
imap.c:1594:message 5357 has been already cached.
file-utils.c:58:TIMING safe_fclose : 0s068ms
procheader.c:197:generic_get_one_field: empty line
I have no idea why it only happens with those three folders.
This has been an issue for quite a while (years, I believe, at least for INBOX
folder).
I just managed to solve the case of Spam and the other folder by renaming the
folder and creating a new one with the same name. The new one is not affected,
even after I copy the messages from the old one to the new one.
Unfortunately, I can't rename INBOX.
I tried to empty INBOX by moving messages into a temporary folder (using the
UI). The tmp folder would open instantly. I then closed claws-mail and removed
the dotfiles (.claws_cache and .claws_mark) in INBOX but as soon as I put the
messages back from tmp, the issue reappears.
I also tried to close claws-mail, delete INBOX folder from imapcache, then
launch claws-mail. claws-mail recreated INBOX folder and redownloaded the
messages from the server and the issue still persists.
Issues that might be related:
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3272
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4243 (less
likely)
I don't know what else I could do to track the issue but the log above seems
like a nice hint already.
Needless to say, this is a bit of an annoyance, especially considering the
INBOX folder is the one affected.
Anything I could try to solve or workaround this?
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list