There's a couple inaccurate things in that article that stood out at me. It should be pretty easy to measure the CPU hit when running ABP. It looks like the author is running windows so he should be able to use perfmon. He also mentions that "As with all proxy servers, though, the one caveat is that it doesn’t work with HTTPS connections" which is very much wrong.
Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
371–380 of 419 posts
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#372> In Nethercote’s testing, he found that TechCrunch used around 194MB of RAM without ABP enabled 194MB for a single webpage that should mainly be text communicating a message. Does anyone else than me find this crazy?
I find that absurdly crazy. My Firefox sessions usually see between 300 to 1200 tabs open at a time. Now I understand why I need to keep crashing it to force the GC. I wish all tabs idle for longer than 5 minutes would be collected by the GC. I just need the tabs open for reference organization (like the History but with nestedness since I use Tree Style Tab) but I don't need all of them in RAM.
I didn't check if they still work with new Firefox versions but there are extensions that exactly do this.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#373Earlier quoted context omitted.
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.
What's wrong with a simple link? I know facebook doesn't want you going down that route, but there's nothing to stop you.
The like button is just one of many of Facebook's components which can be embedded into pages; another being the comment box which shows your name and display picture but cannot allow the hosting page to get at that information unauthorized.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#374I use AdBlock Plus not because I don't want to see ads...I actually don't mind ads. I use it because I don't want auto-starting audio, ever . I have 30-60 tabs up at any given time. When an ad starts playing audio, it disrupts my entire workflow, possibly disturbs my partner sleeping next to me, etc. In short, auto-start audio in ads is quite simply so far outside of what I consider acceptable behavior, that I'm will…
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#375Earlier quoted context omitted.
Ghostery is proprietary software, and it's reporting your usage back to trackers if you enable Ghostrank. You would be better protected running Privacy Badger by the EFF. It's Free Software, and it doesn't track you. https://www.eff.org/privacybadger
> Although we like Disconnect, Adblock Plus, Ghostery and similar products (in fact Privacy Badger is based on the ABP code!) Privacy Badger most likely has the same issue that this article is talking about.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#376Earlier 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.)
Personally, I just don't have Flash enabled at all – it's a security win and I haven't heard my laptop's fans while browsing in ages.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#377Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#378Earlier quoted context omitted.
What's wrong with a simple link? I know facebook doesn't want you going down that route, but there's nothing to stop you.
The Facebook like button tells you when you've already liked a page. It can also show you how many likes a page has, which a simple link cannot do. The like button is just one of many of Facebook's components which can be embedded into pages; another being the comment box which shows your name and display picture but cannot allow the hosting page to get at that information unauthorized.
FWIW, on a site I work for, we use a plain facebook like link without any personalisation because that's all we require, and we recognise that it respects our visitors' privacy more than the full-on iframe variant.
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#379Earlier quoted context omitted.
Well I use it (and I assume most people use it) because I don't want to see ads. Advertising on the web is largely just obnoxious, ugly, and crude. Also the relentless tracking is a little creepy, so there is another small benefit to using an ad blocker. I know there are some small groups trying to do good advertising on the web but it is so insignificant it doesn't even register. Large and important websites don't c…
Glad to see this point of view represented. I have never found the indignant reaction to the use of ad blockers very believable. Advertising is predicated on lies, by definition, and I am only interested in making consumer decisions as far from the influence of marketing departments as is practicable. Advertising is the very worst that capitalism has to offer. Moreover, I am not interested in being distracted by ads,…
Re: Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
#380Edge cases are not completely ironed out but if people want to help perfect it I'll very happily accept PRs !