-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thunderbird freezes during sync of O365 Calendars #695
Comments
This comment was marked as resolved.
This comment was marked as resolved.
Hi @Micke3rd, As far as I can see on the Thunderbird addons page and in the manifest, the latest available version is 4.7, which states it supports until TB 115.*. Therefore, I understand that my environment should work. Even so, this has been happening for a while though (surely before 102 was released), but it seems to be worse lately. I am unsure if the issue belongs here or in EAS-4-TBsync (as I don't know if the freeze comes from the UI or the sync plugin), this could be moved there if more suitable. The issue may be related to jobisoft/EAS-4-TbSync#245. |
sorry, you are absolutely right about the versions. I only looked at the latest release here on the site. |
TbSync is trying to be asynchronously, so it surprises me that it can freeze your computer. Servers may not respond directly which forces TbSync to wait for the answer, but it should not "freeze" your computer. Could you give more details? |
Hi @jobisoft, For instance, the "new message" button will not do anything until some seconds later, and Ubuntu displays the "Thunderbird is not responding" popup. Every time this happens, TBSync is synchronising, though it does not happen every time TBSync syncs (I believe it's only the times when the long wait happens). I have recorded a video, and I sent it over email. |
This happens to me too. Happens on multiple computers both linux and windows. Steps to reproduce
|
I have the same Problem: Windows 10 Version 22H2 Thank you for any idea or solution! |
I have the same problem as neidert on my new laptop with windows 11 23H2. My old PC with windows 10 22H2 does not have this sync problem. "2190/2240 items processed" |
Windows 11 23H2 I now switched to TB and I have the problem that I only get this problem with a certain calendar, 11 out of 12 calendars work without problems. That's very strange because it's nothing special. Sometimes 50 out of 158 elements are synchronized, sometimes 53, sometimes 58, in the debug log the last entry is this one and otherwise everything looks OK.
At the time 10:23:53 TB freeze and TBSync is "not responding" The calendar entries that have been synchronized up to that point are also visible in the calendar in the bar on the right, as long as the TBSync window is open with "not responding". I hope there is a solution for this, because the problem is the show-stopper for me at the moment :-( |
The issue has been open for quite a while now, so I would like to ask whether the root cause of the problem lies with TPsync or if there is another cause for this issue? Thanks! |
Your environment
TbSync version: 4.7
EAS-4-TBSync Version: 4.7
Thunderbird version: 115.3.1
OS: Ubuntu 20.04
Expected behavior
Thunderbird should not freeze during calendar sync.
Actual behavior
Thunderbird keeps freezing when TbSync is syncing. This has happened since Thunerdbird 9x. I experience the same issue in another computer with same OS and accounts. I tried reinstalling TbSync and removing the account with no luck.
I only have an O365 account synced, so unsure if this is on TBSync or on the EAS plugin.
Steps to reproduce
Wait for the sync timeout to happen so that the calendar syncs, or perform a manual sync from the interface. It does not seem to always happen (sometimes manual sync is immediate).
When it happens, I see that one of the calendars says it's "Synchronizing (0/1)". The status is "Waiting for changes", with a countdown. It freezes during this time, also when "Waiting for acknowledgement of local changes".
Debug log sent over email.
The text was updated successfully, but these errors were encountered: