102.1.2 upgrade causes IMAP synchronization issues
Running 64-bit 102.1.2 on Windows 7 (need to maintain Windows 7 as part of my work). When I first upgraded to 102.1.2, the local (synchronized) copies of my mailbox were immediately corrupted. Server copies are fine. I saw, for example, that many key folders had dozens or even hundreds of sub-folders of the same name with a sequence number tacked on (INBOX-0001, INBOX-0002, ... INBOX-1050 for example -- I forget the exact zero padding but it was in the names). I tried a few things then resorted to removing all the local *.msf files for a full rebuild. This is a fairly large set of folders so rebuilds can take a while but this one seemed a lot slower. Then, during the rebuild it would stop and leave some IMAP folders unsynchronized. In some cases this caused filters to fail with "no such folder" type errors. I thought I finally had it fully rebuilt, which involved having to visit each folder, or select sets of folders and compact them. But then, on exit/restart, a bunch of folders were once again out of sync. I have the total messages header set for folders and I'd see big chunks of those empty after restarting -- where I had just painfully got them all sync'ed and showing totals before the restart. The total folder size still shows, but upon visiting the folder it ends up doing a full sync of that folder. Some of these folders have a lot of message so this has become extremely painful. And if visit enough folders it bogs Thunderbird way down running their resync's in parallel (there seem to be a limit to how many though). It can slow Thunderbird way down, to the point of not being able to use it for periods of time ... sometimes the hourglass is also on for a long time (10-20 minutes). The folders are no longer corrupt -- just some subset of them (which seems to move) are continually in a state of resync.
Any ideas appreciated, including any ways to easily resync all folders in a sane way. I have the account set for all to sync but it seems like I either have to visit the ones out of sync or select them as part of a compact operation. Very time consuming and now I'm headed back to the workweek where I need to be able to use this account.
I've checked the physical disk the local folders reside on and it's not reporting any issues (plus I have other things on that disk that are having no issues).
Alle Antworten (10)
Those folder names are the sort of thing that occurs when there is file contention and files are not available when Thunderbird tries to access them.
Things that are knows to be issues.
- Antivirus products scanning files on update/access
- Backup programs that attempt to backup files when they change.
- network latency when the profile is on a local network device such as a NAS
- Latency when the profile is in a cloud synchronized location.
None of those are in play here. Individual folder access to the IMAP server (local) looks fast. The issue is there are a lot of folders and some of those folders have a lot of messages. Anything I try that sync's some in parallel ends up really bogging down Thunderbird.
Visiting folders one at a time takes forever, then the bigger issue being I had already done that but when I restarted Thunderbird later, a random set of the folders I manually sync'ed showed up with no totals in the folder pane (empty, not zero). Those are the folders that end up having to be sync'ed again. If there was a way to resync each folder, one at a time, without having to visit each one manually, I could at least let that run overnight to fill in the gaps each time this happens. The set of folders losing their sync does seem smaller in number as this has progressed but the question is why does it happen in the first place when they're showing as fully sync'ed before restarting Thunderbird?
Geändert am von Wayne Mery
I had to reboot for other reasons and this time the Thunderbird restart seems to have kept most or all of the folders sync'ed. But the performance is now horrible even after it's been running a while. Trying to compose an email, it goes into unresponsive mode for several minutes at a time. Strange, because even while it was sync'ing the folders earlier it was performing at least a little better. Maybe after more time running ... CPU and memory use are both very low.
I reinstalled 102.1.1 and, so far, that seems to have fixed things.
A few more notes that may help. With the last 102.1.2 restart I tried, it was again re-sync'ing some of the larger IMAP folders. The messaging at the bottom just wasn't there until I moved around a bit. I then tried setting the sync to only sync the anything from the last 10 days. That appeared to stop the sync's but it was still really slow. Just moving to the next or previous message with a mouse click could take 15-20 seconds. Again, really odd because I was not seeing it that slow earlier even when it was sync'ing.
Going back to 102.1.1 seems like it's fixed it all.
Spoke too soon. Same basic issues and, once again, about 75% of the folders that were sync'ed earlier appear to think they need a resync. Sync'ing the INBOX at a snail's pace. Network is fine for everything else. Something must have changed with IMAP. I probably made it worse and this may be one factor: When trying to downgrade, Thunderbird would never stop running after exit. I assume it was thinking it had to finish those slow IMAP sync's. I eventually killed it with Task Manager -- otherwise it probably would have taken hours. It was after that when most of the folders lost their total counts and showed other signs of needing full sync's.
I alluded to this above, but what would be useful here would be a way to do a full IMAP sync with some parameters off hours when the sync's seem to bog things down like I'm seeing. Either run it outside of the main Thunderbird at some low priority or set it to run full bore when it's not in use -- somehow run the IMAP sync's in background except for the obvious needs like when you visit a folder that's not sync'ed.
After stabilizing this, what appears to be happening is Thunderbird decides it has to resync IMAP folders for whatever reason and it starts doing a number of those in parallel, which then brings use of the UI almost to a standstill. I've been running checks outside of Thunderbird on which IMAP files/directories it's updating and these are, by and large (90% or more) older folders that have no current updates ... most of them pretty big but where no new messages are coming in. That seems to be the difference with the update: With older releases, once an older folder was sync'ed it was never touched again unless a change (new message, etc.) was detected.
Right now, for example, it's updating 4-5 of these large, unchanged folders at the same time.
Figured out a lot of this was caused by the QuickFolders add-on. With that disabled everything seems normal now. Never had issues with this add-on before but I see some posts regarding recent issues due to differences in the 102 Thunderbird release path.
Big palm to the forehead for me not disabling add-ons sooner.
Something which in the future may save us all a lot of time https://support.mozilla.org/en-US/kb/troubleshoot-mode-thunderbird