Some more info on how Adblock Plus is trying to fix the issue: https://adblockplus.org/blog/on-the-adblock-plus-memory-cons...

Would it have the same problem with a multiprocess Firefox?

It may be worse, the problem is that it loads too many info per tab. If you do it on multiple processes it will not get any better.

Multiprocess Firefox currently only uses one process for all tabs (plus a browser UI process). The tab process will be sandboxed, so users will get some of the security benefits of multiple tabs without the memory overhead of tab-per-process.

If you want to experiment with more than one tab process, you can tweak the about:config pref "dom.ipc.processCount".

Thank you for the informations, I'll experiment.

Whichever one it is for chrome I have, it isn't ABP, it's a generic named Adblock. I don't use ABP due to the developer accepting money to whitelist google adverts.

If you don't like that behavior, you probably wouldn't like Ablock's either: https://palant.de/2014/07/29/which-is-better-adblock-or-adbl...

(Admittedly the author is biased towards ABP. My biases: former Adblock user, former ABP user, current Adblock Edge and µblock user.)

Thanks. Probably going to evaluate http://alternativeto.net/software/ublock/ instead next time I have to use chrome.

AdBlock is significantly worst than ABP memory usage-wise (edit: on Chromium, I didn't benchmark elsewhere). I believe this is also the case CPU-wise from observing Task Manager during benchmarks.