That's all right.Ĭheck for errors associated with AdBlock:
If either Chrome or AdBlock is unresponsive, you won't be able to do this. Next, we'd like you to check for any errors associated with AdBlock or Chrome. If Chrome is still running, a screenshot of the Chrome Task Manager showing AdBlock (How do I use the Chrome Task Manager?).
ADBLOCK PLUS NOT WORKING ON CHROME WINDOWS
A screenshot of the Windows Task Manager or MacOS Activity Monitor showing Chrome (How do I provide a screenshot?).AdBlock's debugging information (How do I give you debugging information?).It will really help if you can provide some information for our developers. (If Chrome is thoroughly hung, you may need to use the Windows Task Manager or MacOS Activity Monitor to end the Chrome process.) If closing the tab doesn't help or Chrome is frozen or unresponsive, restart Chrome.If you can get to the Chrome Task Manager, close the unresponsive tab by ending the process that is using all the CPU.One of these suggestions should help get things moving again: This is what I'm telling folks right now:
ADBLOCK PLUS NOT WORKING ON CHROME UPDATE
It was either an AdBlock (ABP) update or a Chrome update that introduced the issue.
We've been getting these reports for several weeks now. Does that mean that only EasyList is in the list shown in the Advanced tab in the options page or are there also others such as "Allow nonintrusive advertising" and "ABP filters"? You mentioned that you have only EasyList enabled.Which other pages have you encountered this issue on? Maybe we can find something that all those pages have in common.Do you have any other extensions installed? If so, can you try disabling them and see whether the issue still occurs with only Adblock Plus enabled?.Unfortunately, I couldn't replicate the behavior myself yet so I can't look into what exactly is going on myself but I'll keep trying.įor that any help is very much appreciated such as the following information: And I'd expect any synchronous action that takes a noticeable amount of time to also put the CPU at a higher-than-normal level. Because the browser only waits for synchronous actions to finish when it checks back with the extension whether a request should be blocked. The normal CPU usage level, however, makes me think that it may not actually be the extension causing it. The lockup description seems consistent with what I'd expect when the extension is busy doing its thing since the browser waits for the extension to respond before downloading anything. Please test on old and new versions of both Chrome and Firefox. Keep a look out for problems where a site should be whitelisted but things are still blocked, and similar.
But, since I did touch the page/frame logic I recommend testing things like blocking, the various types of whitelisting and element hiding. Since this issue is very hard to reproduce, you might not be able to verify it's fixed. I have not been able to verify that however, since I so far have been unable to reproduce the problem.
0 kommentar(er)
