Open juneyourtech opened 7 years ago
I subsequently added manual excludes in Greasemonkey for the Anti-Adblock userscript to:
Additional note: High resource usage by Firefox visiting flickr (when also using Anti-Adblock) was only with the image search results page in flickr, and not with individual flickr image pages.
The CPU was at 100% all the time. When disabling Anti-Adblock Killer, the throttling ceased. Visiting flickr is usually resource-intensive on my computer, because the PC is old. The Firefox Web Console is also reporting some script issues at flickr itself.
In the Anti-Adblock userscript, I searched for flickr, and added the following excludes:
"yimg.com", "geo.query.yahoo.com", "github.com",
which seemed to reduce constant 100% CPU usage after reloading the flickr page. The fan did still keep going, but eventually stopped.
While the swallowing of event clicks, event mousedowns, and event mouseups seemed to have stopped with this, they really didn't:
After adding domains to the excludes list, the CPU fan went on and off for times. I couldn't tell, though, what exactly caused the Firefox process to still demand more resources after having added domains to the Anti-Adblock excludes list.
In addition, the Firefox Browser Console reported some of the following:
Browser: Firefox 39.0.3 Script manager: GreaseMonkey 3.9 Adblocker: Adblock Plus 2.7.3, NoScript 2.9.0.14 Allowed domains in NoScript when visiting flickr:
Filter lists: Adblock Warning Removal List, Latvian List+Easylist