New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not really an issue : impressive improvement of Firefox 41 for AdBlock #427
Comments
No gain for uBlock as it doesn't use the same method to block ads. |
Doubtful, uBlock does not use global stylesheet to enforce cosmetic filtering, and my understanding is that the Firefox fix applies only to global stylesheets.
I will for memory use. You can also try it yourself meanwhile by following very rigorously the steps of the benchmark: https://github.com/gorhill/uBlock/wiki/Firefox-version:-benchmarking-memory-footprint. However I never performed a benchmark for CPU on Firefox, because I wrote a custom benchmark tool to automate the benchmarks on Chromium, and this tool is not available for Firefox. Using an automated tool ensure the benchmarks are rigorous. Even then, Chromium makes it further easier to measure CPU usage because one can see CPU use specific to an extension in the browser's task manager. |
I can't answer a specific passage on the blog itself, there is no reply button. So here.
That's actually what motivated me to start uBlock more than one year ago, as my answer to the "tech elite bubble" misrepresenting a solution worth investigating for the benefit of users. |
Hello,
Nicholas Nethercote made this news (https://blog.mozilla.org/nnethercote/2015/07/01/firefox-41-will-use-less-memory-when-running-adblock-plus/): it seems they, at long last, patch a very old issue with Firefox, making it lighter in memory usage and also making AdBlock Plus really lighter.
He also said that it would not affect uBlock since it makes things differently.
The questions here are:
It is not like I would switch to AdBlock Plus since I cannot stand their policy.
But I just would like to know.
The text was updated successfully, but these errors were encountered: