UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.62 Safari/537.36

Steps to reproduce the problem:
Run Chromium. 

What is the expected behavior?
That the browser not crash, and also, that it can render windows.

What went wrong?
Chrome closed with no message.
Chrome is unable to render windows.

Crashed report ID: 9d913444-e5ad-4ee3-9a62-b24a28063c1b

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes 67.??? or 68 prior to final version of 68.

Chrome version: 68.0.3435.0  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

I must have recently updated to the final version of 68 (within the last few weeks?) --- it suddenly crashed a few days ago (see debug attached). I don't know if THAT crash is related to the issue I'm now having:

I updated to Chrome/69.0.3448.0.  On this version, if I drag a tab 'out', so that it's its own window, it can't render itself! See attached. 

I can click where the title bar should be, and maximize it, but it's still unrendered: No elements display on the page, and the tab itself is offset to the right (a single tab, instead of being flush left, in a new window, is just sort of midway, anywhere, on the screen).

This is with all windows. This is also in incognito mode.  This is a new thing.  I know this is a new thing because a large part of my workflow is dragging tabs on to various monitors.

This behavior exhibits on the _same_ monitor _and/or_ a different one.  

To 'restore' one of these unpainted windows (which can't be interacted with, unless you 'guess' where the title bar is; any other window on top of it leaves itself) it's possible to SHIFT-ESC to task manager and kill the GPU process (?!).

I checked my flags, which I often mess with to try to make Chrome more reasonable (like enabling things which should be enabled by default --- sitewide tab muting, audio control on tab, etc) for any odd gpu settings or accelerated 2d canvas blah blah blah anything graphic flags set.  Nothing.

I haven't changed anything else on my system. This is definitely an issue in Chrome 69 -- possibly an issue with my older video card. I'm attaching the output of chrome://gpu as well.

And! Typing this and going to paste the GPU to file, I notice there are actually some errors there which may be useful.  

If there's a similar bug to this, please direct me to it, especially if there's some sort of solution.  

Right now, I can easily reproduce this, since literally just opening Chrome, clicking '+', and dragging the new tab out will display this behavior.  This absolutely breaks usability.
 

Deleted: Goddamn_Chrome.png 58.1 KB

	Goddamn_Chrome.png 58.1 KB View Download

Deleted: wdbg_analysis.txt 3.1 KB

wdbg_analysis.txt 3.1 KB View Download

Deleted: chrome_69_gpu_report.txt 49.4 KB

chrome_69_gpu_report.txt 49.4 KB View Download