> ABP has features—like cleaning up Facebook, hiding YouTube comments and other cruft

> did I NOT notice any resource savings

Benchmarking is a tricky matter. One has to be very cautious in order to get meaningful results. Great care has been taken in all my benchmarks in order to obtain meaningful results. Some insights for those who wants to look at memory figures: "Memory footprint: what happens inside µBlock after installation".

Move the mouse to the page's bottom right, a modal dialog is waiting for you to confirm that what is highlighted is really what you want to block.

Look at the screenshot at the top of the article, AdBlock is in there. The own memory footprint is typically closer to double that of Adblock Plus when subjected to same workload. This is not a fluke, it's always how it ends up when I benchmark. I didn't look at AdBlock contributed memory footprint to web pages though…

Sorry about the duplicate posts, they can be deleted. My "Allow third-party cookies" setting was enabled, this was breaking the posting of comment through my Google account.

Personally I use you-block — users have last say. The use of the mu character is just to denote the smaller footprint.

I don't have this problem, ads do not show up. Something must be interfering with your blocker.

If it doesn't block ads in Gmail, that is a bug. uBlock parse and enforce same filters as ABP, so if result is not the same as ABP, I consider this a bug.

If it doesn't block ads in Gmail, that is a bug. uBlock parse and enforce same filters as ABP, so if result is not the same as ABP, I consider this a bug.

If it doesn't block ads in Gmail, that is a bug. uBlock parse and enforce same filters as ABP, so if result is not the same as ABP, I consider this a bug.

I'm guessing it's related to issue #166, which is now fixed. Quite related to what I said above regarding hosts files, the breakage was because Peter Lowe's (PGL) hosts file blocks `liverail.com`, so I had to create an exception to counter the wide rule in PGL's hosts file to un-break the site.

My statement is that the memory footprints shown are representative enough. The way the Chrome API works regarding the handling of net requests is that all extensions are executed to inspect each net request, even if one of them cancels that net request. So basically they have the same workload.

System-wide is definitely an advantage. However there is one disadvantage which makes this solution not suitable for everybody: when the hosts file causes a site to break, you can't un-break the site.

Check "Allow in incognito" for the extension in "chrome://extensions".

In my benchmarks, Adguard was not lighter than uBlock. I may repeat the benchmarks to check with latest versions of all popular blockers. And there is also the fact (I just checked it was still the case) that when you select malware/phishing protection in Adguard, your browsing history is sent to an Adguard server,…

No link to uTorrent. the Greek "µ" letter is not a brand mark. The code is GPL.

Note that in all my benchmarks how I highlight that I always take care to ensure the browser's garbage collector has done it's job.