Date: Sun, 24 Dec 2006 12:01:19 -0800 From: Garrett Cooper <youshi10@u.washington.edu> To: freebsd-questions@freebsd.org Subject: Re: FF 2.0 hogging the cpu in FreeBSD 6.2-PRELEASE Message-ID: <458EDC8F.2030307@u.washington.edu> In-Reply-To: <14989d6e0612231237o6e1aef57u3f44bb3cc42f1e35@mail.gmail.com> References: <499c70c0612231016i2007f7cvd871030f2225f69d@mail.gmail.com> <fb6605670612231049g320b6ba0j5f58f9a242da1ce1@mail.gmail.com> <14989d6e0612231237o6e1aef57u3f44bb3cc42f1e35@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Walther wrote: > On 23/12/06, Michael P. Soulier <msoulier@digitaltorque.ca> wrote: > [...] >> Firefox is a pig on every platform. Plus, more sites are using >> javascript for AJAX these days, pushing more and more load onto the >> client. > > I agree. It's painfull to see that you browse a website and it > consumes all your cpu cycles eventually. Since most of these scripts > are used to power adverts or some graphical stuff that really isn't > necessary, I use FF with the Adblock, NoScript, and > Flashblock-Extension. > Adblock filters known ads, together with "Adblock Filter.G Updater" > you get a decent list of ad placing sites. > NoScript is configured to block all JavaScripts by default, and if I > think that a website doesn't behave as I would expect (e.g. doesn't > react on URL- oder buttonpresses in forms), I temporarily allow > scripts for this site. Sites I visit regularly that require JavaScript > get general permission. > Flashblock teaches embedded Flash-Objects "on demand"-behaviour by > replacing them with a play button. The Animation is only started after > this button is being pressed. > This puts an end to high CPU load... Strange. Firefox 2.0 doesn't appear to be much of a problem for me on my P4 2.4GHz machine. Then again I run NoScript and Adblock by default. Also, if you dig through the tabs in NoScript a bit, it has options to disable Flash stuff by default and then you can whitelist the Flash animation as well. The only problem I have had with Firefox CPU-wise has been caused by annoying, poorly created blog sites (40+ some animated gifs in the background--ate up nearly all my available CPU resources). Another thing, there were some known problems with Firefox 2.0.1 that were addressed with GTK filechoosers, if that's part of what you're doing. -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?458EDC8F.2030307>