Google-chrome – disable console logging for all chrome extensions

I realize this is an older question, but there is a better way than systematically disabling all your extensions to find out which one is throwing an error.

Hover the mouse pointer over the file name for the error in the console. You'll see a long string of gobbledygook. Part of that is an id that is unique for each extension. Take a moment and memorize the first few characters, in the image below they are pmejh:

Then go to your installed extensions at chrome://extensions and hover over each details link looking for a URL in the bottom left of the window that contains the characters you memorized.

Firefox has a way to change the console logging level for specific extensions from about:config.

Chrome doesn’t have this capability. Your options:

1. Filter out all messages from a particular source file by right-clicking the white (blank) part of console message line and choosing Filter > Hide Messages from foo.js. You can undo this filtering from the same menu later, if you wish. Chrome will remember to do this filtering for you until you disable it (even if you navigate somewhere else or restart Chrome).
2. Override one or more console methods. This approach only affects the current scripting context. Chrome extensions run in their own isolated worlds with their own window objects, global scopes, and console objects. If you can’t edit the source code of the extension, you’ll need to paste and run your console-altering scripts in each extension’s execution context, and your modifications will only be in effect until the page is unloaded. You can change the console’s effective execution context using the dropdown at the bottom of the console that says <page context>. Note that any frames or iframes in the page also have their own execution contexts, accessible using the frame dropdown (initially set to <top frame>).