I'm experiencing black screen in google chrome (and a lot more...read below) after waking windows 10 up from sleep mode.
This issue appears in google chrome and all derived applications, in few words I'm experiencing this in:
Google chrome Version 80.0.3987.149 (pretty sure i was having this issue also before)
The new Microsoft Edge browser based on chromium
All the pwa (progressive web apps) installed with chrome or edge
All electron applications like:
Visual Studio Code
Whatsapp
All the Electron applications made by me.
I had this issue for a long time but the spreading of chrome based services is going to make this thing a lot annoying...
I'm using Windows 10 1909 home 64 bit (pretty sure I was having this issue also in windows 10 1903)
WORKAROUND: if in google chrome (or edge chromium) i keep a tab that in the closing prompts a javascript alert, in the moment when the alert is prompted, the issue is gone, the black screen is gone and i can return to see the whole tabs.
So after waking up windows 10 from sleep mode, if i see black screen in the browser i can just close it with the cross in the top right corner, in that moment the alert is prompted "are you sure to leave this page?", i answer "no i want to stay in this page" and the issue is gone.
Of course this is a workaround cause you can forget to keep that site in the tabs of chrome/edge, and this doesn't resolve the issue in visual studio code.
Starting google-chrome with the --use-gl=desktop seems to work with no side effects.
I had same issue with Fedora, Chrome and NVIDA drivers. At first I tried enbling the vulkan flag.
Go to chrome://flags and enable ignore-gpu-blacklist and enable-vulkan. However, Chrome performance suffers and others have pointed out with this settings.
Found the vulkan tip in a comment here. The use-gl-desktop tip here
Related
I cannot make Google Chrome tile correctly in Awesome WM (version 4.3 in Debian 10 & 11). Chrome's window stops responding, or goes blank, if it is resized (a new tile is added next to it, or a tile is closed/minimized), or when it's open in floating mode.
This weird behavior started with the recent version of Chrome (probably, 86). Only Chrome is affected, Firefox and all other applications I use work without problems.
I tried running Chrome with debug log, but there is nothing helpful there. No error messages appear, neither in journalctl nor in ~/.xsession-errors.
Did anyone experience anything like this before?
The problem was resolved after disabling "hardware acceleration" in Chrome. Seems like this feature didn't work well on my system (intel hd graphics 4400 and Awesome WM).
I am trying to debug remote Chrome, the device could be connected, and inspect the tab starts fine.
But in the window of remote debug, everything is a mess. the GUI is terrible, which makes the functionality totally unusable, see picture below:
resize this window or change the resolution is not working.
some times tabs like elements, source, networks could presents, but under the source tab, there is search bar keep presents and covers all area of the codes area.
this is totally not working.
OS: Win7.
PC Chrome version: 63.0.3239.108 (Official Build) (64-bit)
I don't think this should related to Mobile Chrome or android version.
Is there any possible reason for this?
I think Chrome is a widely using browser this can't be a formal released bug for Chrome, right?
I am working on a mobile website at the moment and I refreshed the page, Chrome quit unexpectedly, and since then all touch screen emulation is absent and/or failing.
Chrome Version: 36.0.1985.125 m,
OS: Windows 7 Ultimate SP1
Google Chrome suddenly and unexpectedly stopped emulating devices properly. All touch screen functionality has been disabled and apparently removed. When I emulate a device, the Sensors box fails to be checked and upon inspection, does not show any 'Emulate Touch Screen' option.
I have tried the following, all in conjunction:
Uninstalling/Reinstalling Chrome and deleting all personal settings, including uninstalling all extensions, restoring all defaults, etc.
Restarting the computer
Running anti-virus software
EDIT: Installed Chrome Canary which produced the exact same problem
Please let me know if there are any other relevant details that I might need to add.
Sorry about this. We overhauled the touch emulation in Chrome 36 to be much more accurate (sharing code with what really happens in Chrome Android): https://plus.sandbox.google.com/+RickByers/posts/CBCmhVttj5C. In the process we ended up disabling touch emulation when real touch support was present (at the time we thought this was no big deal because if you've got a real touchscreen why would you want to fake one with mouse?). But some Windows PCs report that they have a touchscreen when in fact they don't really (Eg. Visual Studio installs a touch screen emulator I believe).
We're fixing this at http://crbug.com/395531 - hopefully there will be a Chrome Canary build soon that re-enables touch emulation in these cases.
In the meantime you can mostly work around the issue by disabling Chrome's support for built-in touchscreens at chrome://flags/#touch-events. Make sure you set this back to 'Enabled' after Chrome is updated to fix the issue. With this disabled, some minor aspects of touch emulation (eg. DOM0 ontouchstart= handlers) will not work properly.
Stop the "Tablet PC Input Service" and restart chrome. If chrome thinks you have a touch screen, it won't let you emulate one.
I stumbled across the answer here:
https://github.com/Modernizr/Modernizr/issues/880
For some reason, my tabs have gotten crunched on my google chrome browser (see picture attached). I've try to go into settings and reset browser but it does not change. I'm running windows 8.1 with my fonts at 150% because I have big monitors.
Version 31.0.1650.63 m
I just did some more searching and found the answer (though it makes the screen pretty ugly, google does not do a good job with this)
http://productforums.google.com/forum/#!topic/chrome/BnI6QInBHC4
"I found the answer posted by Azmeer Kahn on November 22. Type chrome://flags in the address and scroll WAY down to the HiDPI section - change from default to Enable. Whew. Worked for me."
Are these tabs pinned? I had similar problems with pinned tabs in early versions of chrome. Unpinning and pinning again might help then.
I'm trying to understand these strange rendering error boxes that are too big to be ignored. This seems to happen on Chrome in Windows 7 (my testing isn't too elaborate) and nowhere else. When I attempt to inspect, they all disappear. This could be some kind of video card issue as I'm using some pretty advanced CSS3 transitions that could mess up memory. In any case, if someone could offer advice on what I could do to fix, I'm at a loss. The site is www.crane-usa.com
Having the same issue with our site using 21.0.1180.89 and 21.0.1180.79. Problem is in Windows 7, Mac OS X latest, Ubuntu and in Chrome frame running in IE9. IE9 with Chrome frame disabled works fine. The problems are intermittent and unrepeatable. Inspect element removes the problem as you say. I tried disabling GPU compositing via chrome://flags but that didn't fix the issue.
We and our users have only been seeing these issues since approx Aug 27, 2012, 3 days ago. I took a look in crbugs.com and found that this seems to have existed for a couple of weeks already. http://code.google.com/p/chromium/issues/detail?id=143647
Sorry our site is not public so I can't post our url but you're not alone.