This also happens in programs that use Blink, such as Discord.

Do you have consistent reproduction steps? If not, it will be hard to track down this
bug.

I don't have steps beyond just leaving a Chrome window in the background and alt-tabbing back after a while. It's probably something you won't be able to reproduce as it doesn't happen to my brother either.

It happens all the time on my PC though. I'll be playing a game and alt-tab back to Chrome or Discord and have black boxes until I scroll or do something.

I can provide any logs or dumps that might help.

Thank you for providing more feedback. Adding requester "chrishtr@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Of note, this also just happened with a Twitter page where holes appeared in the scrim rather than block boxes. See attachment.

Deleted: bug.png 1.1 MB

	bug.png 1.1 MB View Download

I have noticed several issues with long-running tabs in the current beta build (Version 53.0.2785.57 beta (64-bit) OSX)

I do not have a firm timeline for how long it takes before the issue occurs. I will usually leave Chrome active, with multiple tabs open, when I suspend the OS (close laptop).

Upon resuming use, Chrome tabs will display black boxes visually on each tab. Attempting to navigate to a new URL using an affected tab does not resolve the issue. Each problematic tab must be closed.

Opening a new tab in  the same Chrome session appears to work, however old, broken tabs will then mirror the content of the new, good tab. It is difficult to explain, I will try to capture a video. 

Here is a video of the tab cloning (or lack of refresh) after this issue occurs & a new unaffected tab is opened

Deleted: chrome-53-bug-420p.m4v 341 KB

chrome-53-bug-420p.m4v 341 KB Download

This is now in Production Version 53.0.2785.116 (64-bit) Mac

There seem to be two likely unrelated issues here.

jetison.24@gmail.com and cdeely@gmail.com, could you please confirm if these issues are still reproducible.  If yes, could you please attach a copy of the output form navigating to "chrome://gpu/"?

I don't think I've seen it recently. I also had my video card die, so it's possible that was the culprit.

I do still see this occur on a regular basis. I am attaching my GPU output

Deleted: gpu.html 46.2 KB

gpu.html 46.2 KB View Download

Thank you for providing more feedback. Adding requester "vmiura@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]

vmiura@ can you please triage this?

ccameron@ could you please take a look at comment #14 (Mac GPU info).

There are multiple different issues in this bug. The original report is a painting bug on Windows.

Then #10 and #14 are on something going very wrong with the WindowServer.

Of note is that we had some issues in M53 with issue 631485.

Without the ability to reproduce this bug, I don't think we can take any action on it. Adding Needs-Feedback one more time -- is this issue still happening?

I have not witnessed this bug in a few months, possibly as far back as version 54.

Thanks!