Issue metadata
Sign in to add a comment
|
Page fails to render and flickers
Reported by
p...@myitcv.org.uk,
Oct 8 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3230.0 Safari/537.36 Steps to reproduce the problem: 1. Visit http://www.openrunner.com/index.php?id=7583116&dis=173.068&uni=km 2. Sometimes the page fails to render and flickers in parts, particularly as you scroll up and down the page 3. My machine is then rendered almost useless because the graphics card or similar is then in a "bad state" What is the expected behavior? The page renders correctly 100% of the time What went wrong? Page failed to render properly, per repro steps Did this work before? Yes It worked in Chrome on a previous version of Mac OS X Chrome version: 63.0.3230.0 Channel: dev OS Version: OS X 10.13.0 Flash Version: This appears to happen randomly, or put another way I can't seem to find a sequence of steps that causes this to be 100% reproducible. It also happens with https://web.whatsapp.com/, https://play.google.com/music/listen and https://twitter.com/ (particularly when there is a live video in the right hand side column) For example when it happens on https://web.whatsapp.com/ the screen is left only partially rendered state (see attachment). The problem is that when this _does_ occur, it appears to put my machine in a bad state, such that the _entire_ machine then runs slowly, despite the CPU not maxing out in any way. There are also no errors showing in the Mac OS X Console app, nor the browser. Restarting Chrome when it's in this state has no effect; a machine restart is required. This appears to have become an issue since I upgraded to Mac OS X High Sierra (and could be related to https://bugs.chromium.org/p/chromium/issues/detail?id=772725&q=&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified): MacBook Pro (Retina, 15-inch, Late 2013) Mac OS X 10.13 (17A405) 2.6 GHz Intel Core i7 16 GB 1600 MHz DDR3 Intel Iris Pro 1536 MB
,
Oct 9 2017
Unable to reproduce the issue on MacBook Pro (Retina, 15-inch, Mid 2012), 10.13.0 using chrome reported version #63.0.3230.0 and latest canary #63.0.3235.0. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Navigated to URL: http://www.openrunner.com/index.php?id=7583116&dis=173.068&uni=km and https://web.whatsapp.com/ 2. Scrolled up and down. 3. Observed page rendered correctly and did not observe any flickering. reporter@ - Could you please check this issue on latest canary #63.0.3235.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Also please verify the screen cast and please let us know if anything missed from our side. Thanks...!!
,
Oct 9 2017
As I said in the initial report, I don't have a way of reproducing this reliably. Indeed I'm not even sure what sequence of events causes this to happen. It happens about once a day, and when it does I need to restart my machine. But what I will do is, next time it happens, I'll create a screen recording so you can see the visual effect I'm talking about. The WhatsApp screenshot I took last time however is one of the symptoms of when things go wrong. When it does go wrong, are there any steps I can take to collect information, logs etc?
,
Oct 9 2017
Thank you for providing more feedback. Adding requester "krajshree@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
,
Oct 10 2017
As per comment #3, it seems the issue has inconsistent behavior and there are no specific steps to follow in order to reproduce the issue. Hence, removing the Needs-Bisect label as of now. Please feel free to add the same if required. Thanks...!!
,
Oct 10 2017
,
Oct 16 2017
99% sure this is the same issue reported in bug 772735 . Trying to track down the cause. paul@, if possible can you attach the contents of about:gpu to this bug (or the one I'm duplicating to)? navigate to about:gpu and select "save as website, complete". Thank you! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Oct 9 2017