mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 11:35:47 +03:00
[GH-ISSUE #340] Outlook sometimes hangs and does not update incoming email #794
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#794
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jgilbert2017 on GitHub (Jan 28, 2022).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/340
(version 4.0.0.0)
I'm seeing some sporadic issues where Outlook hangs indefinitely and does not update incoming email.
The UI is responsive but the tray icon is stuck in the "updating" state and new mail does not show up.
Outlook will also hang on exit and need to be killed in the task manager to restart.
I've captured a memory dump and the hang is in VSTA_Main but the stack trace is just memory addresses (no method names/symbols). I'm not using any other plugins/addons other than outlookcaldavsynch.
How best to debug?
@Dim3nsioneer commented on GitHub (Feb 7, 2022):
same issue here with V4.1.0
@jgilbert2017 commented on GitHub (Mar 11, 2022):
i still can't get a stack, but a possible hint indicates a file system operation failing (possibly due to excessive NTFS fragmentation???).
wish i could get a stack so the issue can be directly handling in the code, but for now i'm going to try cleaning up my disks and defragging to mitigate.
@jgilbert2017 commented on GitHub (Mar 19, 2022):
after defragging i still got a hang. attaching a debugger to the running outlook.exe process does not give any stack or tasks :-(.
does anyone know if there is a flag / registry setting etc that will force outlook to host the vsto addin in a debug mode?
@jgilbert2017 commented on GitHub (Mar 19, 2022):
possible issue-
SynchronizerFactory.CreateHttpClientdoes not set theTimeoutproperty on theHttpClient. Tracing the code it looks like this is only used for timezone info fetching inGlobalTimeZoneCachebut i suppose it could be a problem.@jschiefer commented on GitHub (Jun 30, 2022):
Seeing the same issue with 4.2.0, syncing with Nextcloud 23.
@GregorB54321 commented on GitHub (Oct 23, 2024):
unfortunatelly I can not name a reason, but with 4.4.1 I still have that or a very similar issue. Outlook gets unresponsive and Mousepointer is alternating between pointer and sandtimer two to three times a second. I also suppose it is somehow network related.
@GregorB54321 commented on GitHub (Nov 4, 2024):
may this helps?
log.txt:
log.txt is logging since years in debug, size around 460MiB. May this impacts performance also?!
In the long running reports the "Invalid email address" line is repeating a couple of times (10th to 100th times) every 10-60secs. Still blaming about the same Recipients.
@scroguard commented on GitHub (Dec 3, 2025):
i too am experiencing this issue. the only way to get outlook to update when this occurs is to exit and re-open it. however, once the program attempts to sync the calendars again, outlook will stop receiving e-mail.
strange thing is the status window shows a green check mark next to all the the sync profiles.
@scroguard commented on GitHub (Dec 3, 2025):
ok, i have a little more information on this issue now. i'm watching the status window and even though i have the synchronization interval set to 30 minutes, it appears that the sync keeps restarting on a couple of the calendars. it appears that these calendars get caught in an endless loop, which apparently ties up outlook and prevents it from being able to move on to keeping the inbox in sync. i have recorded a screen capture of the sync status window to show what is occuring:
https://github.com/user-attachments/assets/efcb59e3-aacc-4b8a-b933-2a27aa1ae862
looking over the log file, i do not see any errors.
@GregorB54321 commented on GitHub (Dec 3, 2025):
It maybe is related to unresolvable recipients via IMAP / Exchange... (just a suspicion)