Do you only see glitches like this with DevTools debugging?

It looks to be an issue with the graphics card or the GPU compositor's handling of surfaces. Over to the GPU team.

The NextAction date has arrived: 2017-06-11

@ schenney@chromium.org

Sorry, I assumed I'd get notifications on activity but didn't so haven't seen your question. 

In answer yes I only see this when I'm debugging with DevTools. I also have a colleague who has exactly the same problem on identical hardware. Some information about my machine from DxDiag:

Machine: Dell XPS 15 9550
OS: Windows 10 Pro 64-bit
Display: Intel HD Graphics 530 
Render: NVIDIA GeForce GTX 960M

Thank you for providing more feedback. Adding requester "schenney@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

 Issue 711311  has been merged into this issue.

Are the texture lost/corrupted?

Sorry to bug you again ipwright83@, but if you wouldn't mind navigating to "about:gpu" saving the page using (save as webpage, complete), and attaching that here, it will ensure we know exactly which GPU/rendering modes are active on your machine at the time the glitch is seen.

I wonder if this could be related to  crbug.com/734058  - could also be a synchronization issue. We'll need to wait for GPU info from that bug to know for sure - although that was a new M59 regression, so maybe unrelated.

Thanks!

Adding Needs-Feedback for the request in #8.

Sorry about the delay (is there a way to subscribe to this thread?)

I've attached the GPU information as requested. I guess the visual output is a little different to that other bug - there are hard lines that are wrong in this issue, whereas that you can see the equivalent of scan lines. Though I haven't seen it in a few days.

I'm not sure how to respond to the textures being lost/corrupt - what would be the visual indication of that?

Deleted: gpu.htm 53.6 KB

gpu.htm 53.6 KB View Download

Thank you for providing more feedback. Adding requester "vmiura@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

ipwright83@, thanks for the additional details! Looking at the about:gpu, I see a few non-standard GPUs listed (vendor 0x17e9). Do you have any usb monitor adapters attached?

If so, does the issue reproduce when using those monitors (either as a secondary or primary monitor)? I know you said you hadn't seen the issue recently, so I'm curious if it has to do with the specific display device being used. Thanks!

ericrk@ since posting I've actually witnessed it occur another couple of times.

You're actually correct regarding the USB monitor. I've put a breakdown of my current setup:

Primary - Dell monitor connected HDMI->DVI
Secondary 1 - laptop screen
Secondary 2 - Dell monitor connected via a Dell USB adapter similar to (http://www.officenerd.co.uk/info/dell-adapter-usb-c-to-hdmi-vga-ethernet-usb-30-da2-1332445?gclid=Cj0KEQjwhMjKBRDjxb31j-aesI4BEiQA7ivN-CfKgq6Dbh1t29xP6tNMUo2QrWxqMlHFIknvt3iarNwaAmut8P8HAQ)

I doubt it'd make any difference, but the USB adapter is daisy chained out the back of the USB hub on my primary connecting to the Secondary 2.

I've seen this issue so far on both my Primary and Secondary 1, I don't recall seeing it on Secondary 2 (USB one) but that's probably because I don't run DevTools on there often, however I'll endeavor to do so to see if it occurs there too.

Thank you for providing more feedback. Adding requester "ericrk@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

ericrk@ so I've just confirmed that this also occurs on my monitor I detailed as Secondary 2.

Some other information I've managed to find out is that it only seems to occur when DevTools is maximized. In fact I had it maximized on one monitor, dragged it to another (while dragging the window is not maximized and renders correctly) and as soon as I snapped to another monitor it re-maximized with the same rendering issue. Shrinking the side of the window again (without dragging) also causes it to render fine.

What may also be interesting (which I hazard a guess points to GPU issues) is that when I've tried to capture this maximized / non-maximized behavior using a Screen recording tool (Screen2Gif) is that DevTools doesn't exhibit the behaviour as reliably - it's hit and miss as to whether it will render the black areas, while it's pretty consistent without the screen recording.

I've also failed to reproduce this on any other tab, other than the [Elements] tab thus far, but the rendering bug only affects the docked lower console.

Deleted: Black Boxes.gif 4.9 MB

	Black Boxes.gif 4.9 MB View Download

This sounds a lot like issue 606152 (linux, intel, maximized windows only).

@enne are you sure this issue is a duplicate? I've asked in the other thread 
about my setup and someone suggested that they've only seen it on old graphics cards - whereas I'm running on a fairly new XPS.

I'm also using Windows and have no flicker - unlike that bug?

I'm un-duping this issue, as this is on Windows with GPU Rasterization rather than One-Copy.  It seems it may be related to using a USB display adapter or other multi-GPU issue.

Reporter: I wonder if you would be able to confirm if this issue still happens on a recent Chrome Canary?

I've seen this today on the Rendering tab - Version 60.0.3112.113 (Official Build) (64-bit)

Deleted: Capture2.PNG 80.1 KB

	Capture2.PNG 80.1 KB View Download

The NextAction date has arrived: 2017-09-29

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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