Hello - I have run into the same issue. Findings:
* Disabling the ESET add-in in Outlook 2016 causes Outlook to behave normal and ESET not to spike.
* Enabling the ESET add-in in causes an average of 15 seconds delay loading Outlook 2016 profiles.
* Closing Outlook 2016 with enabled ESET add-in causes Outlook to hang and not close. ESET services spiking to over 1GB and c. 14% CPU. Hard termination through taskmanager causes ESET to remain at c. 1GB and 14% CPU levels long after Outlook 2016 services have stopped. Memory leak keeps building up.
* Running Outlook 2016 with disabled add-in, and then enabling the add-in causes ESET services to spike temporarily to c. 1.5GB and then drop to 650MB. After that, it steadily climbs to between 850MB and 1GB. Outlook 2016 becomes unresponsive when enabling the add-in while Outlook is running. Procdump runs into errors and stalls.
System: i7 4790K CPU, 16GB RAM, 64 bit Windows 10.
I have (Procdump) dumps available for 3 scenarios:
1) Running Outlook 2016 with ESET add-in disabled. (Dumpsize c. 280 MB)
2) Add-in enabled- with Outlook closing. (c. 950 MB)
3) Outlook closed (through taskmanager) and then reopened with add-in disabled. (c. 1.1 GB)
Additional note: I have been using ESET for years and find that these issues occur now and then with new updates of either the engine or signature database. Running fine for several months and then running into these issues until the next update comes out. That said: Running the same setup on another system does not necessarily correlate same observed issues.
Please advise how/where to provide you with the dumps / info for analysis. This is causing me a lot of issues currently.
Regards
