Jump to content

ESET products freeze Chrome tabs


Recommended Posts

This seems related to this.

 

I'm currently using EIS 11.1.42.0

I've been happily using ESET products for nearly 10 years. 
There's one thing that always happens and hasn't been fixed, ever - on any of my PCs where I have ESET installed.

Every now and then, when I do something inside Chrome, like switching a tab, typing, scrolling, the application hangs for 2-5 seconds. At that time, "ekrn.exe" consumes a bunch of CPU cycles. After that, everything is back to normal.

I don't mind that ekrn scans on access, but I've added the chrome.exe, my temporary folders, the chrome temporary folder and everything I could find, Chrome-related, to exclusions.
Protocol Filtering is off.

Once I disable Real-time file system protection, the issue is gone.

 

Please tell me how I can properly exclude Chrome from *any* ESET protections altogether. This is driving me insane. It has been happening for years, on multiple machines (home and work), with EES, ESS, EIS, EAV.

 

Thank you.

Edited by panni
Link to comment
Share on other sites

OK. Disabling Real-time file system protection doesn't fix it.

I've disabled ALL features in EIS currently, and ekrn.exe still eats CPU occasionally and freezes tabs in Chrome. This is a clean installation using ESETUninstaller beforehands.

Link to comment
Share on other sites

"C:\Program Files\ESET\ESET Security\Modules\em008_64\1506\em008_64.dll" is the module that consumes the CPU cycles when that happens.

Edited by panni
Link to comment
Share on other sites

  • Administrators
6 hours ago, panni said:

"C:\Program Files\ESET\ESET Security\Modules\em008_64\1506\em008_64.dll" is the module that consumes the CPU cycles when that happens.

Did you analyze a memory dump or how did you find out? The dll is loaded by ekrn so you can't simply check it it the Task manager. Also that module has nothing to do with real-time protection, it's a firewall module.

If pausing real-time protection actually makes a difference, please generate a Procmon log with advanced output enabled as per the instructions at https://support.eset.com/kb6308/ while the issue is occurring.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...