Live data from Hacker News

Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

extremetech.com

331–340 of 419 posts

Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

#331
post #2

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

Thanks for the recommendation! Long time ago I've uninstalled AdBlock due to the noticeable performance issue and have been suffering the ads on the news websites, will now try uBlock.

Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

#332
post #57

Noscript is not an option anymore. Too many sites rely on javascript. I'll take the memory hit every time to use adblock.

You'd be surprised. I use JS-blocking on a blacklist basis, but previously I was using a JS whitelist: the first week or two was a little annoying as I remembered the ~dozen sites I use that required JS for their use. After that though, the vast majority of the one-off sites that I'd visit were content (like articles etc), and for those the actual desirable content is usually completely visible without JS (and everything loaded a heeeell of a lot quicker). Maybe once a month I'd come across a site that did something stupid like load the article text through JS, and if I felt like it it's quick couple of clicks on the Chrome URL bar to whitelist the domain for JS.

Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

#333
post #179
post #57

Noscript 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.

In case you're on Chrome, this is allowable (and super-accessible) by default, by clicking on the icon at the beginning of the URL bar.

Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

#334

Earlier 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.

Both the DNS and the transparent proxy sound like an interesting way to improve the web at home (I'm thinking specifically of an iPhone on my WiFi) -- do you have more information about how you did these things?

Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

#335
post #279

They 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.

> The best resource-friendly browser on OS X is Safari.

You may find others having an opposite experience:

http://i.imgur.com/qfwwXhw.png :)

Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

#336
post #2

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

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.

iirc, ublock also blocks api.google.com (i guess it's the analytics javascript files?), which incidentally, also breaks a lot of sites that uses the google common javascript library CDN (which servers stuff like jquery etc). I whitelisted it and it seems to unbreak some stuff.

Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

#337
post #289

Earlier 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.)

in which case, i use the inspector and delete the html element containing the ad overlays.

Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

#338

Earlier 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.

iframes are the only unit of isolation on the web. Unless you want the like button you're hosting to have complete unrestricted access to your application's private data, then yeah, the like button needs to be in an iframe.
Post reply on HN