False Positive on sessionstore-1.js

When I open Firefox, avast has gotten a hiccup on a firefox file sessionstore-1.js as a suspicious file. I told it to ignore.

Strange… It shouldn’t. I’m using FF and avast fully updated and not a trouble.
Submit the file to virus total.
Is your avast fully updated?

If I remember rightly this happened some time ago in 4.8 and I added an exclusion to the standard shield. Now looking at the file system shield I also have that exclusion (see image), which must have been carried forward from my install of avast5 over avast4.8. Though I believe my path even with the * wildcard at the front is different to where the profile session info is held, so it wouldn’t be valid.

You should send a copy to the chest and then send it to avast for analysis. There is a possibility that there might be something in there from previous session, you could check that out at virustotal.

Tried to upload the file to virustotal, 0 bytes received. Got an error when trying to upload it to NoVirusThanks Multi-Engine Virus Scanner.

Hi Jtaylor83

With a modern computer (800mhz or faster) the sessionstore creating should not cause any slowdown. However, an antivirus program could decide that the updating of the file was a reason to scan the whole directory or could fight Firefox for permissions to the file. I suspect you could have also told the antivirus to not scan the firefox folders and that would have fixed it also. If you have security software scanning and locking the temp file sessionstore-1.js and maybe sessionstore.js as well then you can have the hang that you experience. There is no need to let security software mess with files in the profile folder. That will only cause problems and can cause file corruption,

polonus

Create a folder called Suspect in the [b]C:[/b] drive. Now exclude that folder in the File System Shield, Expert Settings, Exclusions, Add, type (or copy and paste) C:\Suspect*
That will stop the File System Shield scanning any file you put in that folder.

Close Firefox to that.

Firefox isn’t the problem, it is avast blocking a file that it has alerted on as you aren’t trying to move what firefox is trying to use but copying it to VT.