Screen flickering after resume from sleep
Reported by
kenny.st...@gmail.com,
Jul 16 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9745.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3157.3 Safari/537.36 Platform: 9745.0.0 (Official Build) canary-channel kip Example URL: https://www.facebook.com/events/856665204481379/ Steps to reproduce the problem: 1. Load up the event page in question 2. Flip to the Facebook news feed 3. Go back to the event again What is the expected behavior? Facebook should still look good without any ugly flickering or random color changes What went wrong? See attached screenshots ― don't know if it's GPU or what, but it causes everything from a whitening of the top bar to flickering of the page and everything in between. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 61.0.3157.3 Channel: canary OS Version: 9745.0.0 Flash Version: Shockwave Flash 26.0 r0 Thank God for the canary builds ― better that I experience this nuisance than someone else who may not know what to do should it happen.
,
Jul 19 2017
Update 2: Seems to only be a problem after resume from sleep. Today's update [Chrome 61.0.3160.0; Platform 9759.0.0 (Official Build) canary-channel kip] did not fix this problem.
,
Jul 27 2017
,
Jul 28 2017
Workaround: enable chrome://flags/#enable-fullscreen-app-list In the latest few updates, that launcher has assumed a strange tendency to sporadically override the old one on resume from sleep, which still wants to show itself ― the conflict between those two launchers trying to run at the same time could be the culprit.
,
Jul 29 2017
This bug's progression follows this pattern: Initial startup: old, mid-screen launcher First resume from sleep: full-screen launcher Second resume from sleep: flickering mess As stated above, enabling chrome://flags/#enable-fullscreen-app-list is a workaround, which means that a fix would entail enabling it by default.
,
Nov 8 2017
,
Nov 10 2017
,
Nov 10 2017
,
Nov 14 2017
The bug is pretty old, and we couldn't repro it. I'm closing it; if this still happens with newer CrOS versions, please reopen. Thanks for reporting! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kenny.st...@gmail.com
, Jul 16 2017