Zen11t 6 Posted February 1, 2019 Share Posted February 1, 2019 After a time ESET Agent start using of 50% CPU continuously. Win 7 Enterprise 32 bit virtual machine on XenServer 7.0 Thanks, Zen11t Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted February 1, 2019 ESET Staff Share Posted February 1, 2019 Couly you please create memory dump of ERAAgent.exe process (in this high-CPU usage) and provide them to use either using private message, or through support ticket in case it was opened in the meantime. We have similar reports only from WindowsXP/Windows2003 systems to this time. Also does 50% CPU means that there are are only two cores/CPU available for this machine? Link to comment Share on other sites More sharing options...
Zen11t 6 Posted February 4, 2019 Author Share Posted February 4, 2019 I restarted the vm, but I will create memory dump next time. Yes, it has 2 cores available. Link to comment Share on other sites More sharing options...
mtrento 0 Posted February 18, 2019 Share Posted February 18, 2019 (edited) hello, I am struggling with this random issue aswell . every day i receive a call from some users complaining for a slowdown of their virtual pc. The agent version is 7.0.577.0 , i had issue with previous version too. only a reboot can fix (temporally) the issue i have provided a memory dump of the process. regards edit : i opened a support ticket [Ticket#5049737] , as per instructions received , i generated a full memory dump of the machine. note: as this issue occurs on a random basis and because the machine is virtual, i used the suspend trick to obtain the memory dump Edited February 23, 2019 by mtrento provide a full memory dump Link to comment Share on other sites More sharing options...
Zen11t 6 Posted March 7, 2019 Author Share Posted March 7, 2019 @MartinK I send dump file in PM. Thanks, Zen11t Link to comment Share on other sites More sharing options...
mtrento 0 Posted March 7, 2019 Share Posted March 7, 2019 hi, i just received the answer of the support: note :i have provided memory dumps and all required logs: Quote thank you providing us with additional logs. Due to the nature of this issue I have asked our developers for help. They have already replied to me that this issue is already reported as bug. It appears that this is aimed to be fixed in ESMC v7.1 which is planned to be release in 3rd quarter of 2019. As of now there aren't any workarounds Link to comment Share on other sites More sharing options...
Zen11t 6 Posted March 7, 2019 Author Share Posted March 7, 2019 @mtrento Thank you for the info, so we wait ESMC 7.1 Link to comment Share on other sites More sharing options...
Recommended Posts