ATtached an example of this occurring.

Deleted: chrome_tabstrip_regression.png 50.3 KB

	chrome_tabstrip_regression.png 50.3 KB View Download

This looks to me like some sort of DWM or similar bug -- Windows should not be trying to draw the standard window titlebar when we've explicitly asked it not to, except in weird cases where the system thinks the app is unresponsive and wants to give you a close button (but then it should say "[Not responding]" or similar in the window title).

Rob or Bret, you have any idea how to figure this out?

To clarify, is the screenshot from Win10? That looks like a WinVista/7 era window frame with DWM disabled.

Hmm... I've seen something similar but it when I was doing mean things to the window styles, so that's not very helpful here. Otherwise I have no clue.

Adding Allen and Ananta because this is more up their alley.

It's happening on two completely different Windows 10 Pro machines of mine. Both have all normal Windows 10 full animation/compositing/DWM stuff enabled to the best of my knowledge. My machine at home is running an Nvidia GTX980, as it's a gaming machine. Both have dual displays (work one has triple display.)

This happens SUPER consistently. It takes only a couple minutes for it to occur, usually when I'm in the window but not doing anything, but it will also happen if the window is behind other windows out of focus. 

I'm also not running any themes as best I can tell ("reset to default theme" is grayed out in settings.)

Can I output any telemetry/config to you guys? I'm especially vexed that two  different Win10 machines are causing this, so I'm trying to think through what commonalities I have. I just launched an incognito window and almost immediately, it did it again, though I don't know if incognito would stop themes/something else from triggering.

Deleted: more_tabstrip_issues.png 368 KB

	more_tabstrip_issues.png 368 KB View Download

I'm expecting to see the attached frame (File Explorer) for Win10. What does the File Explorer frame look like for you?

Do you have any custom Windows themes set?

Deleted: Win10 Frame.PNG 7.0 KB

	Win10 Frame.PNG 7.0 KB View Download

It looks identical to that, except I use Windows' "choose a color from my background picture to set windows title bar color" feature, so it's typically colored. That's why you see a color in my original screenshot. In fact, that's consistent on both. I don't use Windows themes, but that's baked into Windows. Might be reproducible if you try to set a color? Or have it auto set? 

Here's my explorer window.

Oddly, my laptop also running Win10 with colored themes doesn't exhibit this artifacting.

Last night, my primary desktop also had the tabs flowing over the window controls, so I couldn't minimize the maximized Chrome window. 

Deleted: this_pc.png 27.6 KB

	this_pc.png 27.6 KB View Download

What Windows setting did you use to change the title bar of the File Explorer? Changing the accent color doesn't seem to work for me.

Right click on desktop, personalize, colors, select "show color on title bar".

However, I just disabled that and went back to white and still am exhibiting the issue...

Deleted: more_artifacts.png 1.3 MB

	more_artifacts.png 1.3 MB View Download

Deleted: color_titles.png 104 KB

	color_titles.png 104 KB View Download

I know you're busy with real work, but is there any telemetry/settings/config things I can send your way to help narrow down what this might be? 

I'm confused as to why this would occur on 2 of my 3 Win 10 machines which all run synched Chrome. 

I've attached a gif of this behavior occurring. Please note that the gif has some minor artifacting (lines across the screen, or a bit of white on the tabstrip) that is from the creation of the gif, not from Chrome rendering. 

In the first instance, I resize the window and it almost immediately occurs. It's cleared when I scroll the page. In the second instance, it happens shortly after switching to a new tab and pausing. But clears as I change focus on to another window.

Deleted: chrome_artifact.gif 467 KB

	chrome_artifact.gif 467 KB View Download

The biggest thing we need is a repro. Until then, we're just speculating.

I've verified that your window frame in theory can at least appear in Win10, but only when DWM is off. Your instance is particularly interesting because non-DWM assets are being shown while DWM is running. The positioning, however, is a little off (icon and caption buttons are too close to the edges).

It may be useful get a process memory dump.

WARNING: The following will crash your browser! You may need to restart it and you may lose data.

1. In the address bar, navigate to the below URL. ***This will crash your browser, resulting in potential data loss.***
chrome://inducebrowsercrashforrealz
2. Restart Chrome (if it hasn't done so already) and then navigate to chrome://crashes
3. Note the crash ID (in the form of a GUID) and add that to this bug.

Thanks!

Deleted: Screen Shot 2016-09-15 at 4.45.23 PM.png 27.5 KB

	Screen Shot 2016-09-15 at 4.45.23 PM.png 27.5 KB View Download

Here you go: crash/97eaefee00000000

I started a fresh instance of Chrome (after killing all processes) and opened a new tab, immediately saw The Flickering, and then crashed the hell out of it. 

Here's another, just done immediately after for the hell of it:

crash/71ae31bd00000000

Crashed my home computer as well:

Crash ID: crash/71974ff500000000

Just as an additional data point, I upgraded my work computer from my workstation NVS310 display adapters to a GTX750Ti and... same result. Still exhibiting this behavior. 

My next troubleshooting attempt will be to nuke this installation from orbit and re-install without syncing extensions or anything else to see if it's maybe something with a weird configuration, though that doesn't explain why my 3rd, synched computer, doesn't exhibit it.

Completely reinstalling Chrome from scratch with no extensions still exhibited the behavior.

Are there any other Windows options or settings I should look at as commonalities I can play with to see if I can narrow this down? Or would installing Chromium maybe be worth looking at?

If a clean reinstall led to the same issue, that suggests that drivers may be involved. I saw Logitech loaded into Chrome's process on one of the crashes.

Did you use the Windows provided drivers or does your setup require additional drivers beyond what Windows can provide?

Huh. That's really, really interesting. I was using an old/expanded version of SetPoint that allowed for more in-depth configuration on my mouse. I use this on both platforms where I have this bug.

I've switched to a newer mouse and I'm using the current version of Logitech's options app, and not using that SetPoint anymore... 

I'll see if it happens again, but I'm not able to reproduce right now, when I was able to readily reproduce before.

Why would the mouse driver bind to anything Chrome at all? Think we might have tracked this down...

 Issue 649428  has been merged into this issue.

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot