-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"chrome-extension://mnojpmjdmbbfmejpflffifhffcmidifd" errors when disabling/enabling shields #6828
Comments
@kjozwiak retest in 1.2 to see if this is still an issue. |
@rebron looks like this is still happening with the following build:
Example of the error that's being displayed in the terminal when disabling/enabling shields:
|
I'm seeing these kind of errors on today's build off the
Maybe worth reopening this ticket? |
Filed new ticket at #13216 |
Version 1.30.89 Chromium: 94.0.4606.81 (Official Build) (64-bit)
As far as I know I am not doing anything with shields . . but Brave keeps locking up after a while and these errors are commonly the last in the log file when I kill Brave . . |
I have a very similar thing happening as to @philiprhoades II get the following output in the terminal I am running a jupyter notebook every time i open a new tab, and do some other actions. It usually doesn't seem to affect performance, but i did not request this output via any commands.
|
Description
When disabling/enabling shields,
chrome-extension://mnojpmjdmbbfmejpflffifhffcmidifd
will produce errors in the terminal as demonstrated in theActual result
section below.Steps to Reproduce
0.70.122 Chromium: 78.0.3904.87
or0.70.123 Chromium: 78.0.3904.97
--enable-logging=stderr
Shields
Actual result:
Expected result:
Shouldn't be seeing the above errors when disabling/enabling shields.
Reproduces how often:
100% reproducible when going through the above STR.
Brave version (brave://version info)
Version/Channel Information:
Yes
Yes
Yes
Yes
Other Additional Information:
N/A
N/A
N/A
Miscellaneous Information:
CCing @brave/legacy_qa @bsclifton @rebron @petemill @cezaraugusto
The text was updated successfully, but these errors were encountered: