Firefox Problem

Hi Eset.

I've been using ESS 4.2.64.12 and noticed that Firefox takes too long to open (approx 10 seconds) lately. Usually it opens very fast, like only 2 seconds.
I haven't installed any new software so far, so what's the problem here?

Thank you.

 

Could you check the size of the file "%APPDATA%\Mozilla\Firefox\Profiles\%Profilename%\sessionstore.js" ?
Does excluding it make a difference?

 

Hi Marcos.

I don't know cause it seems like I'm having trouble on finding that file you said above.
Anyway, I've already tried to disable the protection of ESS temporarily then I opened Firefox again and it's back as fast as it used to be (took only 1 second). So my guess is that the problem comes from ESS.

Thank you.

 

Firefox stores information about open tabs or visited sites in the above mentioned js file which can grow to dozens of MB. Since js files are thoroughly scanned for script malware, under specific circumstances it may take seconds to scan sessionstore.js.

 

Done that but still no change at all

Thank you.

 

Since the first time I installed Firefox, I've made the settings so all history (including browsing history, temporary files, cache, cookies, stored username & password, site preferences, etc) will be cleared when Firefox closes.
So I think that is not the problem here

Thank you.

 

Have you downloaded any add-ons lately? Those and Firefox checking for updates during loading of the browser may cause it to take longer than usual.

To test whether or not ESET is involved, you could always temporarily disable protection, check Firefox's start time and then re-enable protection. I've always experienced long lag whenever loading Firefox for the first time after a reboot of the system.

 

If disabling real-time protection makes a difference, I'd suggest excluding the js and htm? extensions from scanning for a test, one at a time. Narrow it down to the particular option will shed more light.

 

I'd say that's a good guess.

 

No, I haven't downloaded any add ons lately.
And yes, I have tried to disable the ESS protection temporarily as I've mentioned before in the above post.

Thank you.

 

Done that but still no luck

Thank you.

 

Does disabling real-time protection make a difference? If so, generate a Procmon log at the point the issue occurs, compress it, upload it somewhere and PM me the download link.

 

Thanks, Marcos.