Interesting. I'm surprised you're having this behavior in Chrome 51.

Is there anything being logged to the console?

can you take a screenshot when this happens? 

Hi Paul,

here you go. There are two errors.

The second error seems to not count as a website error: there is a "1" on the right hand side of the red cross error indicator directly when the page loads, but the console appears only later in the drawer when the second error is also shown in the console tab then above the drawer while the 1 is not incremented.

I cross checked with Google Mail. There, I receive one error which is also indicated besides the red cross ("GET https://plus.google.com/serviceworker.js net::ERR_INSECURE_RESPONSE"), but the drawer is not forcefully shown.

So maybe it's the SourceMap error, which is handled by dev tools in a different way than the other errors? That source map is indeed a monster, with the original js being 6 MB. We will split that up later using require js... The framework of choice, Ember CLI, unfortunately throws everything into one file by default.

Deleted: vendor.map.zip 1.8 MB

vendor.map.zip 1.8 MB Download

Deleted: chrome-console.png 201 KB

	chrome-console.png 201 KB View Download

Hi philipp2k7@, thank you for the screenshot and the really helpful cross-check!

Our "Failed to parse sourcemap" is rigged to add a console error AND open the drawer, but it really shouldn't.

This core issue popped up in an earlier ticket #603750, but I made the wrong call back then.  Users who aren't interested in console errors shouldn't have a drawer forced open.  I'll start a CL to make it just add the error without opening the drawer.

Disabling the source maps actually fixed the issue for me. The console is now not coming up on every page load, yeah :-)

Thanks for your support!

This is a really annoying problem :(

Any updates on when this will be fixed?

Disabling sourcemaps is definitely not a solution for me since I need sourcemaps

The underlying problem is the sourcemap wasn't valid so we couldn't apply it. So even if we sort the error message being annoying, your sourcemap is still broken.

I've put in a fix for the annoying message though: https://codereview.chromium.org/2169213002

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6577e9c2199e226fb59c1b15fcc8dc89e245752b

commit 6577e9c2199e226fb59c1b15fcc8dc89e245752b
Author: paulirish <paulirish@chromium.org>
Date: Fri Jul 22 06:19:30 2016

DevTools: Sourcemap failure shouldn't open console drawer.

BUG= 624038 , 497094 

Review-Url: https://codereview.chromium.org/2169213002
Cr-Commit-Position: refs/heads/master@{#407079}

[modify] https://crrev.com/6577e9c2199e226fb59c1b15fcc8dc89e245752b/third_party/WebKit/Source/devtools/front_end/sdk/SourceMap.js