People are using µBlock now for precisely this reason. https://github.com/gorhill/uBlock/wiki/%C2%B5Block-vs.-ABP:-... https://chrome.google.com/webstore/detail/%C2%B5block/cjpalh... https://github.com/gorhill/uBlock
Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
331–340 of 419 posts
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#332Noscript is not an option anymore. Too many sites rely on javascript. I'll take the memory hit every time to use adblock.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#333Noscript is not an option anymore. Too many sites rely on javascript. I'll take the memory hit every time to use adblock.
I use Yesscript, which allows blacklisting of specific sites.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#334Earlier quoted context omitted.
Hosts files only work when the ads and other trash are not served from the same domain, and of course the bigger operators do everything they can to make you lose some critical functionality if you block their ad serving IPs. So you'll need to go to the URL level at a minimum if you don't want to use some important functionality.
Actually this very rarely happens. I a DNS server on my router which has zone that routes all ad hosting & other wanted stuff to an IP which is then rejected by the firewall. I also have a transparent proxy rewriting all web pages removing IFRAMEs - this does ocassionally break things, but it's extremely rare to find a site that actually has a use for them other than serving ads.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#335They are memory hogs with or without particular extensions. I leave Chrome with 10 basic tabs open and in 4 hours, it's already "using" 2GB of RAM. The new Firefox Developer Edition with "process per tab" is similar. The best resource-friendly browser on OS X is Safari.
You may find others having an opposite experience:
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#336People are using µBlock now for precisely this reason. https://github.com/gorhill/uBlock/wiki/%C2%B5Block-vs.-ABP:-... https://chrome.google.com/webstore/detail/%C2%B5block/cjpalh... https://github.com/gorhill/uBlock
I find ublock breaks many more websites than ABP. I usually wouldn't notice a broken website with ABP, but with ublock I see something wrong at least once a week.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#337Earlier quoted context omitted.
Just enable click-to-play in chrome, on media plugins. Sound only ever really auto-plays from flash ads and such (though these days its possible with HTML5 and this likely won't stop such audio/video). Its an extra click and can make some sites a bit more difficult (e.g. beatport, tries to hide its flash so you cant click it to enable it), but it works for me.
Click-to-play on plugins often breaks sites that use Flash ads as overlays. The ads often have the "close this ad" in the Flash code itself, making it impossible to kill the ad layer without activating the plugin. (In my more cynical moments, I wonder whether this behavior is by design.)
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#338Earlier quoted context omitted.
Actually, that's not crazy. Ads, social widgets (the Facebook Like button), third party comment boxes, etc. all render in iframes.
No, they may render in iframes; iframes are certainly not a requirement for any of those features, and some (the original commenter included, I suspect) might consider them a heavy-handed approach to the problem.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#339You don't need an add-on for that. Firefox and Chrome both have this as an optional built-in feature. I think it should be on by default (which it sadly isn't).