The extension failed to load properly. It might not be able to intercept network requests.

[TESTER-sec]

[gorhill]

Do you have other content blocking extensions installed -- disabled included?

[garry-ut99]

A duplicate of:

• The extension failed to load properly. It might not be able to intercept network requests. #109

(Don't spam with duplicates, next time post in already existing threads, search issue tracker before creating a new thread (and in case you already did it, do it better next time)).

[TESTER-sec]

Do you have other content blocking extensions installed -- disabled included?

No. Just uBOL.

A duplicate of:

• The extension failed to load properly. It might not be able to intercept network requests. #109

(Don't spam with duplicates, next time post in already existing threads, search issue tracker before creating a new thread (and in case you already did it, do it better next time)).

Uhm, I did not spam anything., I did search and saw issue 109, but it was closed. I do not make reports to closed reports.

Be better, instead of being a jackass to people that are giving you their free time to help your project.

[gorhill]

No. Just uBOL.

Given this, I will confirm this as duplicate of #109. Sometimes when the extension updates there is an "internal error" reported at the console. Restarting the extension fixes the issue. This is out of control of uBOL, as the error occurs somewhere in the browser's extension framework.

[gorhill]

Actually, given more thoughts, since uBOL should be able to detect the error condition, I will add code to force a restart the extension when such detection occurs. Whether this works or not is purely a guess, will find out with time if this makes such reports go away.

[gorhill]

I was able to reproduce the issue in my local build as I prepared for a new release.

The previously committed code didn't work as expected, and since I was to reproduce at will (as long as a force-reload of the extension was not performed), I could test the code which purpose is to work around the issue. So this is confirmed fixed with gorhill/uBlock@ff57f01.