Firefox users, can you help please, does avast work ok without Firefox lagging

Voted: Avast seems ok with Firefox, I have not noticed problems.

Type of device (netbook, multicore desktop etc): Both a HP Pavilion G series Laptop and HP Presario SR1710NX desktop
Type and version of Avast: Version 7.0.1456
Operating system and version: Windows 7 and Windows XP service pack 3
Firefox version (e.g fx13 or fx14 or ESR): Version 13.0.1

Caveat: The only issue I have is Dial-up related that has to with an occasional series of 17 Dial-up connection prompts that will cause freeze up problems if the connection is used (must be cancelled) of which I really doubt is related to the issue discussed here in as much as only a handful of people are likely using Dial-up in the first place.

Works fine here but my FF is little different
1.It always work at low priority
2.I don’t use the newest flash player
3.Don’t save cache to the hdd
4.Don’t use the WebRep plugin.

PC
Avast Home 1456
Windows XP
FF 13.0 with more than 50 add-ons installed and a lot of other modifications but it still load everything fast

As Flash 11.3 issues are now being mentioned maybe it is ok to comment on that. So some more Firefox related information

No problems here. :slight_smile:

Thanks for all the replies.

I conclude Firefox should work ok with Avast.

Obviously with all software some users will have problems, and inevitably some will be using Avast and Firefox whilst seeing problems, but it appears there are many experienced users who are able to use both together without any problems.

I will go back to the original Firefox forum thread and mention that in my opinion the problem is NOT due to use of Avast, and I will point to this thread as information or anyone who considers Avast is a problem with Firefox.

1.Did you tried starting FF in Safe Mode - this to check if some add-on is doing this
2.Did you tried running FF in Private Browsing Mode - if the FF history or session store is corrupted
3.Check in avast file shield settings in the exclude settings if \firefox\profiles*sessionstore.js exist and only write is checked

Adding

ProtectedMode=0

to mms.cfg should not be necessary, because mozillaZine states (stated?) 11.3.300.262 disables Protected Mode by default. I’m assuming .265 does the same.