New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 782392 link

Starred by 2 users
Status: WontFix
Owner:
█ marc...@chromium.org
Last visit > 30 days ago
Closed: Jan 2018
Cc:
danakj@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Parts of the screen keep flickering between content and black, or older content

Project Member Reported by w...@chromium.org, Nov 7 2017 
Chrome Version: 64.0.3255.0 
OS: ChromeOS Panther

What steps will reproduce the problem?
(1) Sign-in to ChromeOS and use it for a while; I have ~4 windows open, with a total of ~20 tabs.

What is the expected result?

Screen is displayed normally.

What happens instead?

Every so often the screen will suddenly start to flicker between the current content, and some older content, or blank content.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

Comment 1 by w...@chromium.org, Nov 7 2017 

Adding a screen-shot to illustrate what I'm seeing.
Screenshot 2017-11-07 at 13.31.40 - Display 1.png
199 KB View Download

Comment 2 by danakj@chromium.org, Nov 7 2017

Components: -Internals>Compositing Internals>GPU
Owner: marc...@chromium.org

Comment 3 by danakj@chromium.org, Nov 7 2017

Status: Assigned (was: Untriaged)
What further info should we collect to help triage marcheu? It sounds like a driver problem to me.

Comment 4 by w...@chromium.org, Nov 7 2017 

Attached the contents of about:gpu, which show a load of errors and warnings.
gpu.zip
10.5 KB Download

Comment 5 by danakj@chromium.org, Nov 7 2017 

The glCreateAndConsumeTextureCHROMIUM is almost always noise, it happens whenever a renderer closes with textures in flight for instance. If you see those logs appear at the same time the problem occurs then it would indicate some kind of compositor bug, but given there's only 2 it doesn't seem likely.

Some of the "texture unit 0 is not renderable" errors are in basically every about:gpu also, and at least some come from the glCreateAndConsumeTextureCHROMIUM case. Not sure if all.

Comment 6 by mfomitchev@chromium.org, Jan 11 2018 

Dupe of  issue 781060 ?

Comment 7 by marc...@chromium.org, Jan 23 2018

Status: WontFix (was: Assigned)
►

Sign in to add a comment