Describe the bug
When opening a page with MetaMask-enabled Chrome, and developer tools are open, two console warnings are observed:

DevTools failed to parse SourceMap: chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/contentscript.js.map
DevTools failed to parse SourceMap: chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/inpage.js.map

To Reproduce (REQUIRED)
Steps to reproduce the behavior, libraries used with version number, and/or any setup information to easily reproduce:

I have MetaMask 7.7.7 installed in up-to-date Google Chrome Version 80.0.3987.132 (Official Build) (64-bit) on Windows 10.

I press F12 to open the browser console.

When I navigate to any site over http(s), (e.g. https://www.google.com/) I get the above two errors.
By viewing chrome://extensions/, I verify that the nonsense string corresponds to the id for my MetaMask extension.

Expected behavior
No console warnings, ideally because the browser can find and parse SourceMaps. (This would also be helpful in debugging other issues and possibly fixing them via the open-source process.)