White Screen on Previously Functional Websites
Reported by
zacharyc...@gmail.com,
Oct 12 2017
|
||||||
Issue description
Chrome Version : 61.0.3163.100
OS Version: OS X 10.11.6
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Load binance.com
2. Load an issue on self-hosted Gitlab.com
3.
What is the expected result?
- On both of those sites (which I frequent regularly without issue) I should be able to see the content on the webpage.
What happens instead of that?
- The page flickers the content and then just shows a blank white age.
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
,
Oct 12 2017
I'm having the same issue after the recent Chrome update on mac. It happens when there is too much to render apparently (?), because I noticed it when my React code with <3 elements was always rendering perfectly fine, but when I was adding 4th element, screen would just go blank (despite everything being seen properly in HTML source). And one more completely blank site: https://www.mozilla.org/en-US/firefox/new.
,
Oct 12 2017
Switching to Google Chrome Canary helped, it doesn't have this bug there.
,
Oct 13 2017
Unable to reproduce the issue in MacBook Pro (Retina, 15-inch, Mid 2014), 10.12.6 using chrome reported version #61.0.3163.100. Following are the steps followed to reproduce the issue. ------------ 1. Launched chrome browser and opened binance.com. 2. Observed that the page loaded and content of the webpage was seen as expected. Attaching screen shot for reference. zacharycooner@ - Could you please check this issue by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Oct 16 2017
I face this issue constantly this last week on Google Sheets. I use Chrome extensively at work and this is a productivity killer. Even a hard refresh doesn't fix it. Incognito mode doesn't fix it. The same google sheets all render fine in FF and rendered correctly in Chrome until last week. Might be a Chrome vs OSX High Sierra thing.
,
Oct 16 2017
If you're experiencing this issue, can you please attach the contents of "about:gpu" (navigate to about:gpu - save-as website-complete). I think we have a fix for this which we can try to get into the next Chrome release, but about:gpu info will help us confirm we aren't missing anything.
,
Oct 16 2017
,
Oct 16 2017
Glad to hear it - attached.
,
Oct 16 2017
#7 is the same issue (GPU vendor id = 0 and device id = 0) #8 is different because it's correctly identified as a dual GPU (NVidia/Intel) system. We have this device in house. Eric, can you test it locally with OSX 10.13?
,
Oct 18 2017
This issue seems to be nearly exclusive to the Google Document family of properties - I use sheets and docs a ton and sheets is unusable while gmail works intermittently.
,
Oct 18 2017
Same issue on Chrome 61.0.3163.100, OS X 10.12.6. Pages affected, in addition to all those reported here previously: - https://travis-ci.com/ - https://rollbar.com/ See attached about:gpu page. If it's GPU vendor id = 0 and device id = 0 I'm looking for, then that's what mine says too. Can also confirm this is fixed on Canary (64.0.3243.0).
,
Oct 18 2017
# 7 and #12 are the issue discussed in this bug, which we have a fix for. #8 appears to be issue 773705 , which we're working on, but is actually quite hard for me to reproduce (even though I have identical hardware). ram@, please follow along with that issue for more updates.
,
Oct 19 2017
FWIW just updated to latest stable (62.0.3202.62) and the bug is fixed there as well. No need for Canary anymore.
,
Oct 23 2017
FYI Neither this nor 773705 are likely my issue. I'll search around a bit more for existing bugs but might open a new one.
,
Aug 1
,
Nov 21
*** UI Mass Triage *** As per c# 14 closing this issue.If you feel this issue should still be addressed, feel free to reopen it or to file a new issue |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by zacharyc...@gmail.com
, Oct 12 2017