![]() |
|
#1
|
|||
|
|||
|
After 30 hours of uptime with version 6 RC ekrn.exe is has 950MB of RAM for it's Memory (Private Working Set). If I wait until it hits 2GB it will stop updating and it can not be uninstalled/repaired until after a reboot (to stop the service). If I try an update or uninstall/repair before it hits 2GB of RAM usage it works fine.
The same thing occurs with any 5.x version. It does not occur with 4.x versions. With version 4 I had my computer on the entire month of September without a reboot and without the RAM usage going over 200MB. I am running Win7 Pro x64 with all updates. I do use Comodo Firewall but I have tried uninstalling it and the memory leak still occured after reboot. I have added Comodo to the eset ignore list and vice versa with no effect. |
|
#2
|
||||
|
||||
|
It may help to submit a support request online with ESET Customer Care and please include a SysInspector log so they can more quickly troubleshoot the issue.
__________________
Resources: Knowledgebase • Facebook (US) • @ESET • @ESETNA • Support • News • Blog • YouTube: ESETKnowledgebase and esetusa |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|