104

I am developing on Rails5 with jQuery. All of a sudden, this afternoon, I started getting these messages in my DevTools console. It happens even running DevTools under StackOverflow. I cleared cache, restarted the browser with no change.

Searching for a solution, I ran across 44315460 When do browsers download sourcemaps? but I don't even know what to do with that.

OBTW, clicking on any of the links generates "ERR_FILE_NOT_FOUND".

I have no idea how this started nor how to fix it. Advice?

DevTools failed to parse SourceMap: chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/sourcemaps/onloadwff.js.map
DevTools failed to parse SourceMap: chrome-extension://gnldpbnocfnlkkicnaplmkaphfdnlplb/ContentScript/CustomisedWorkItemMessaging.js.map
DevTools failed to parse SourceMap: chrome-extension://gnldpbnocfnlkkicnaplmkaphfdnlplb/ContentScript/CaptureBrowserEvent.js.map
DevTools failed to parse SourceMap: chrome-extension://gnldpbnocfnlkkicnaplmkaphfdnlplb/ContentScript/CustomisedWorkItemMessaging.js.map
DevTools failed to parse SourceMap: chrome-extension://gnldpbnocfnlkkicnaplmkaphfdnlplb/ContentScript/CaptureBrowserEvent.js.map
Richard_G
  • 1,237

6 Answers6

106

For me it helped to only enable current context in devtools.

Selected context only checkbox enabled

Caveat: It is not sticky. You have to reset it every time you open DevTools.

Caveat: API calls to other domains won't show any errors as they belong to a different context.

Webber
  • 1,174
49

I have filed a Chromium issue about this:

https://bugs.chromium.org/p/chromium/issues/detail?id=1052872

I think the multiple recent reports here look as if this is a new bug coming from an upgrade to Chrome.

It's also happening for me on a React/Webpack project which I'm working on which was building fine without this problem before.

I could not find any duplicate except for an old issue which I don't think is the same.

EDIT:

It's a bug! Partly in Chrome, partly in some of the extensions. It won't affect how the extensions work. The feature which is not working, loading source maps from extensions, should be irrelevant for end users of extensions and it was always not working, it's just that now DevTools is flagging the error.

NB If you are seeing this error for your own source map files when trying to debug under HTTPS... it's a different bug! Which is tracked but may take some time to fix.

Fix?

If you're happy to lose the extension then as per other answers here, click on the links in the failed messages, then look just to the left of the address bar (not in the main window) to see which extension you need to disable.

enter image description here

If you need to keep the relevant extensions enabled, then either @Webber's answer using Selected context only works well (but it won't stay set when you close and re-open Chrome), or OP @Richard_G's suggestion of a filter looks good (and stays set) - but I found the suggested filter was cutting out too much stuff:

Try just -chrome-extension as a filter instead, as demoed in the images below.

enter image description here

enter image description here

enter image description here

MikeBeaton
  • 731
11

Same thing started happening with us since yesterday. I think this issue is related to an update pushed by Google on 7th Feb.

https://chromereleases.googleblog.com/2020/02/beta-channel-update-for-chrome-os.html

As per the answers / comments till date, it seems these 3 extensions are affected.

Adblock: cfhdojbkjhnklbpkdaibdccddilifddb
LastPass: hdokiejnpimakedhajhdlcegeplioahd
Test & Feedback: gnldpbnocfnlkkicnaplmkaphfdnlplb

For me, temporarily disabling these extensions worked, but a more permanent solution would be to raise a bug report.

It is also possible that this release made few extensions incompatible, so maybe we should wait for extension creators to release a compatible version.

Another temporary solution would be to allow extension to load "On click" or on "Specific Sites".

Like This

Anand
  • 231
  • 1
  • 2
  • 3
4

Today it was happened to me too. It looks like some extension related chrome behavior is changed after chrome update.

A workaround to get rid of warnings is;

  1. Click the map file link
  2. Chrome shows which extension on the left of address bar
  3. Disable that extension

After disabling the extension, warning is gone.

H. Alper Tuna
  • 41
4

I have a temporary bypass which is kind of ugly. Hopefully, the vendors will get this worked out among themselves. What I did was to add a negative filter to the console settings, as follows. I am not going to mark this as an accepted solution. 

-DevTools failed to parse SourceMap: chrome-extension:

Within a screenshot: enter image description here

Richard_G
  • 1,237
2

in my case it was Adblock Plus - free ad blocker 3.8 extension which you can get rid of message by disabling this extension

Eric Aska
  • 121
  • 2