33

Is there a way to prevent extensions from showing up in the console of the developer tools window? It's annoying to be looking for JavaScript errors and have to ignore errors that are always there. I know from this question you can use Incognito mode, but I don't want to have to develop in a separate browser window with all of the shortcomings of Incognito mode.

If there isn't a good answer to this, how do I run down the offending extension, short of turning them off one at a time?

13

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:

screenshot of extension error in Chrome dev tools

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.

enter image description here

  • Instead of hovering, Chrome now shows the ID so you can do a Find with "command/ctrl-F" to immediately jump to the extension. – Praxiteles Jan 8 '17 at 19:31
  • @Praxiteles On the extensions page, you'll need to check the Developer Mode checkbox to show the IDs. – Quiver Nov 14 '17 at 16:23
14

I know that this is an old question, but coming here today I found a new solution and decided to add my two cents.

In the Chrome console there is a gear option on the far right. Clicking on it will reveal a few options.

Make sure that you are showing only logs from top, and that Selected context only is selected.

This will hide all errors from extensions.

screenshot

  • This looks like the best solution for the problem - great find! – Ivan Peevski Aug 7 at 2:37
6

In case the error is coming from a chrome extension you don't want to disable, there's now a feature to filter messages from specific extensions or scripts. Find the console message, right click on it, go to Filter > Hide Messages from ______. The effect seems to persist for as long as you have that tab open.

chrome console filtering messages

1

Never did find an answer, but I did find the problem by shutting off each extension until I found the culprit.

  • 1
    Is there a better way to find culprit extension? Currently, I also find it in the same way as you did. – IsmailS Jul 18 '12 at 5:57
  • One thing I've since noticed is the dropdown at the bottom of the console that says "<page context>" by default. If you click that, it looks like you can filter to just a single extension, but unfortunately the extension names aren't in there, their reference ids are. – Tom Jul 18 '12 at 16:55
  • The reference IDs are also used in the Chrome Web Store in the address bar. Check this out: stackoverflow.com/a/22820109/230167 – Bryan Downing May 31 '14 at 2:34
  • 2
    @iSid Go to Windows -> Extensions. The extension ID is in the details of each extension. This ID will be shown in the error in the console. – Cooper Maruyama Jun 14 '14 at 11:21
  • 1
    Is there any other way to hide this? I don't whant turn of or delete it, becouse I use it! – Neo Dec 6 '14 at 11:18
1

Here is the way to identify the breaking extension directly. Nonetheless, this is not really the answer to the question. Well - the only way for now seems to be to disable the extension.

Three steps to identify broken extension

Best, Benedikt

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.