Morisato

Anyone tried the updated version yet? 8.0.304 from 301. Not sure if the mem leak was already addressed but I am still getting 262mb from ekrn.exe.

Leaving it on for a few days to a few weeks gradually does make the memory usage to 230-256mb.

Win 7 x64 Idle with no scan. Upgraded from 7 to 8. Only mem leak issue but no high cpu issue.

All this time I was thinking it was related to a RAM issue since Nov, 2013. (Interactive Policy Option as well) https://forum.eset.com/topic/1420-process-not-ending/#entry7841 Bascially when running an app that connects to the net and is not on the firewalls policy list, it should pop-up a notification to allow/deny etc. Sometimes it will not do that and will bascially lock the .exe in place which denies termination via task manager or Unlocker. When it does show a pop-up and then quitting and running the app again (if you only temp allowed/denied), it would sometimes not show the pop-up at all which may lead to a half-loaded app/app crash (which when terminating the task from desktop view will remain in the task managers process list). This forces a user to reset/reboot in order to free up the apps from locked state by ESET. This has never happend in previous versions of ESET before and only started happening in v7 from what I can tell. I am currently on v7.0.302.26 where this still occurs but will try the newer v7.0.317.4 in hopes that this issue is addressed. Really annoying and I hope this gets fixed if it hasn't already been fixed.

Well it's been about a week now and no more process locked into background. I can safely say it had something to do with the scan on execution as that was the only option I unticked. Well it was the only option I had left ticked as I unticked scan on file open and file creation before. Any reason why this might be the case Marcos? Other than that I consider this solved now.

Could be the HIPS. I'll mess around to see if I can reproduce it. In the meantime I unticked Scan on execution and so far haven't experienced any more locked processes.

Well I can safely say its the Eset SS firewall itself. Something has changed or some module update has changed within its functioning where it sometimes doesn't show a popup at all when there are incoming/outgoing connections where it hooks onto the process in which its suppose to bring up a popup but does not. Similar to the other threads where the graphical glitch just shows a popup window with no info on it. I rebooted first to terminate the .exe successfully since its under administrative priority so I couldn't terminate it in any other fashion or form. Once booted into win7 I disabled the Eset firewall first to run the process again to recreate the condition it but I was able to terminate it successfully without it remaining in background. I re-enabled the firewall thereafter and ran the process again but this time it showed the connections pop-up as it should. Once I allowed/denied and terminated the process did it successfully terminate as intended. For whatever reason, it seems the eset firewall interactive mode connections pop-up isn't doing its usual intended pop-ups as before so something must've changed recently on how its handling these processes that initiate the connections pop-ups. If anyone knows of what recently changed in perhaps the firewall modules, please let me know. v1153 20131028 was the last known update of that module in particular and I think its messed with the interactive mode a bit. Maybe Marcos can take a look at it when he gets the chance. P.S. For some reason IE11 won't let me copy/paste on this forum... had to use Fx

Seems Eset firewall is trying to hook into process but never brings up a notification or whatnot to show the usual allow/deny access. This started recently from what I gather and I do not know why. Every time I try to end some processe through task manager it denies me a termination. As I mentioned before it started recently (say maybe a week or so ago). I am not sure what modules you've changed/update to handle things now but is anyone else is having the same issue as me with ESSv7? I think its related to ESS since I never had a process stuck before with ESS installed but whatever updates that recently took place now its somehow keeping my processes in background after I have closed them.

Hmm guess I found another same issue topic here as well. Glad I saw this one too since Macros didn't bother responding yet to the other thread after my post. I can say though Alt-F4 does close it and then it pops up another outbound traffic which actually has the info on that process it was trying to access before prior to closing it. Does this help with the issue at hand or a possible fix in the future? This has never happened in the previous Eset versions that I have used since the v2 days. At least we have a temporary fix for this ambiguous popup.

I too have this issue as well. Just occurred today. Another time it showed a previous scan result along with the recent one from context menu scanning. Clicking on it then pressing F4 does nothing as well. Hope this gets resolved in a future update asap because I can't close it without rebooting the system as well. I noticed that while this blank notice is in place, any processes you run thereafter will remain as a running process until you reboot. Meaning if you opened an app or game then exited, it will still be running in the background and cannot be terminated as ESET will be somewhat communicating with it and/or locked it. Another beef I have is not being able to exclude certain files from scanning after it gets detected as a false positive and placed in quarantine where the option is greyed out. I hear that it needs to auto quarantine twice before it's available but I have never ever been able to get it to be clickable till this day since it was implemented and file exclusion removed (into a more tedious form of adding files to exclusion). Option should be available to advanced users and then be able to manually just delete entries in the File Exclusion list rather than have to manually add the whole folder address through numerous clicks.