I have noticed that when I run Firefox (3.6) in Avast’s sandbox the CPU rockets to 100% usage and stays like that until I close the sandbox. Also IE, and anything else for that matter. :-\
At present I’m wondering whether it is just as well to revert to 4.8, but when does support for 4.8 end?
This has been reported in another thread. It’s apparently a bug with the @ tags. If you have the option to show @ tags in the window of sandboxed applications, try turning it off to see if it resolves the issue.
Why do you need to sandbox Firefox?
I know, it’s a problem, but there is no reason to lose protection of the whole computer and get back to 4.8…
Yes, you are correct, I remember changing that setting earlier today. Now unchecked and CPU back to normal. Thankyou 
Yes, actually, that’s a good question. I’m often wondering whether it’s slightly moving towards the wrong side of overkill as well. More habit than anything I suspect; I’ve just got used to using Firefox through Sandboxie. Really I suppose with Firefox and the NoScript, Adblock Plus, Ghostery, Better privacy, Beef Taco, and KeyScrambler addons installed as well, plus Avast running, there’s not really much to worry about. But I suppose it’s not a bad thing because I’ve never been infected, well not accidentally. I’ve deliberately run virtual machines naked to see how long it took to get ‘whacked’ and it’s probably those experiences that also make me veer towards the paranoid…I’ll stop now…the answer could go on because I ramble a lot ;D
I know, it's a problem, but there is no reason to lose protection of the whole computer and get back to 4.8...
Just me being petty. Sorry. Just used to the ways of 4.8 and some of the newer features in v6 were beginning to aggravate me a bit. For all it’s obvious wonders, v6 seems to be getting a bit ‘laden’ and I have been looking at it negatively…worried it is becoming too bloated, with all due respect. I noticed the installer is now twice the size of v5. I hope it doesn’t keep increasing and get weighted down with ever more non optional tools that aren’t totally necessary.
The SafeZone seemed like a good idea at first, until I checked it out it and discovered the Chrome browser ‘inside’…so I am unable to run Firefox inside it. I get why, but I use the password manager in FF to save all my passwords, so it would be a nightmare trying to remember them…well I couldn’t. I tried importing them but the Chrome browser doesn’t seem to autofill the form fields so pretty much useless. My Internet Banking password is just too complicated to remember so I rely on a separate password manager for that (and others). How would I access that inside the SafeZone? As I say, seems like a good idea until you hit the problems. And, then, when you’ve decided it’s not for you after all there’s no way to remove that feature…which seems like it could be a significant part of the Avast install. I don’t know why that feature couldn’t be modular and an optional install. So, Avast is getting much, much better in a lot of ways, but it seems to be getting worse in others as well.
The removal of the event logging is quite annoying, to say the least. I always head towards Event Viewer at the first sign of problems to see what is going on. It’s a centralisation of system and application events, and as AV software is supposed to be as transparent as possible and integrate with the OS, I’d expect the logging to occur where it did in 4.8. And there’s not even any way to configure paths to the logs. I have a folder on my drive named \WINLOGS and inside that all apps that don’t use System Event Viewer and produce logs have there own folder and I configure, where possible, the logging to those folders. Having to hunt around each app for logs is PITA. So I’d like to see more so-called ‘expert’ settings that allow for more config options. I mentioned in another post about shell integration as another possible user configurable option. Being able to ‘turn it on and off’ within Avast, and even choose which items appear on the context menu as well…which I would prefer. etc. ad nauseum…
Sorry, seems all negative, but it’s not really.
yeah someone has reported a similar issue in the German section, 100% CPU load with firefox sandboxed. I checked on my system and I do not have this issue.
Here’s my thread on this subject…
http://forum.avast.com/index.php?topic=72347.0
I sent them a ticket and I got a reply a few hours later indicating that they had fixed it in an internal build, but no dates as to when it’ll be made public as of yet.
For me, I just removed the red border and left “Show tags” empty as well since it runs all my browsers in sanboxes automatically.
Regards,
R
Yes, I have just installed the beta, and turned borders and tags on and the CPU is not winding up. Excellent.
Have anyone of you guys experienced a sandboxed Firefox screen going black and only shows the red borders…? I see this whenever I print a webpage via Foxit Phantom (AIS ver6.0.1000) or PDF-Xchange Viewer Lite --in laptop also AvastProver6) ???