- by tgm1024, a day agoRated 1 out of 5Causes the 20 "/usr/lib/firefox -contentproc" processes to baloon up to 26.4 GB (WITH A "G") each of *virtual* memory! If I disable it and restart they go back to ~2GB. If I re-enable it (don't have to restart) it jumps to ~32GB Each. All 20 processes.
(Linux Mint 20.2).
- by Pixusman, a day agoRated 5 out of 5Easy to use, but deeply configurable and no noticeable impact on resource usage. Sticking with it for now. Blocking lists enabled by default already do the trick, but if you are looking for an advanced or specific (e.g. social medias) blocking I would advice you to look into third party filters.
- by Firefox user 17156146, 2 days agoRated 3 out of 5This Adblocker was alway awesome until recently. Somehow ads that were blocked before, are now everywhere. I block them, but they return after I refresh the page. That is unfortunate. Other adblockers are slowing down firefox...
- by Firefox user 12440208, 2 days agoRated 1 out of 5It was the best content blocker around until one week ago or so, when I updated my system and it started to make Firefox crash on the Facebook website. It crashes every few minutes, when one tries to change the audience of a post, check who reacted on a comment and on a few more occasions. Firefox 94.0.2 on Debian 11 here.