Zimbra Shutdown Addin prevents Outlook from closing properly
Posted: Thu Nov 30, 2017 2:51 pm
Hi,
I'm currently developing an Outlook addin using Add-in-Express, and I have a problem that is (at least partially) related to this Zimbra Shutdown Addin.
Sometimes, when opening a new mail window (Inspector), then closing the main Outlook window (Explorer), Outlook never stops completely.
The process stays alive with a grey icon in the systray, and it uses 100% CPU time on one core.
What I've found so far:
- The problem only happens on Windows 10 (I tested it on a clean Windows 7 VM (the bug never happens), and a clean Windows 10 VM (the bug seems to always happen), with a release build of my test addin)
- When tested on live Windows 10 machines, it seems to happen more frequently on some machines than on others, but I've not been able to figure out why.
- The problem only happens when the "Zimbra Shutdown Addin" is loaded (I disabled everything except this Zimbra addin and my addin. The version of Zimbra is the latest available: 8.7.10.1711)
- The "Zimbra Shutdown Addin" and my test addin both work properly when they are the only addin loaded.
- When activating the full log for the Zimbra Connector for Outlook, I see that after Outlook tries to close, it gets stuck in an infinite loop processing the same Windows message (from the log: "Dispatching message 0x738")
- I don't know what this Windows message means, but I found someone with a strangely similar problem here: https://fleexlab.blogspot.fr/2017/06/pa ... ezing.html - It says that this 0x738 message appeared in Windows 10 1703, which would explain why I can't reproduce the problem on Windows 7.
So to sum up, it seems to be an interaction between the Add-in Express addin, and the "Zimbra Shutdown Addin", and I believe the Zimbra plugin might be mishandling this new 0x738 Windows message, causing an infinite loop.
This problem seems closely related to that one viewtopic.php?t=62793 that never got any answer...
I'd really appreciate any help on this topic...
Thanks.
I'm currently developing an Outlook addin using Add-in-Express, and I have a problem that is (at least partially) related to this Zimbra Shutdown Addin.
Sometimes, when opening a new mail window (Inspector), then closing the main Outlook window (Explorer), Outlook never stops completely.
The process stays alive with a grey icon in the systray, and it uses 100% CPU time on one core.
What I've found so far:
- The problem only happens on Windows 10 (I tested it on a clean Windows 7 VM (the bug never happens), and a clean Windows 10 VM (the bug seems to always happen), with a release build of my test addin)
- When tested on live Windows 10 machines, it seems to happen more frequently on some machines than on others, but I've not been able to figure out why.
- The problem only happens when the "Zimbra Shutdown Addin" is loaded (I disabled everything except this Zimbra addin and my addin. The version of Zimbra is the latest available: 8.7.10.1711)
- The "Zimbra Shutdown Addin" and my test addin both work properly when they are the only addin loaded.
- When activating the full log for the Zimbra Connector for Outlook, I see that after Outlook tries to close, it gets stuck in an infinite loop processing the same Windows message (from the log: "Dispatching message 0x738")
- I don't know what this Windows message means, but I found someone with a strangely similar problem here: https://fleexlab.blogspot.fr/2017/06/pa ... ezing.html - It says that this 0x738 message appeared in Windows 10 1703, which would explain why I can't reproduce the problem on Windows 7.
So to sum up, it seems to be an interaction between the Add-in Express addin, and the "Zimbra Shutdown Addin", and I believe the Zimbra plugin might be mishandling this new 0x738 Windows message, causing an infinite loop.
This problem seems closely related to that one viewtopic.php?t=62793 that never got any answer...
I'd really appreciate any help on this topic...
Thanks.