Issue metadata
Sign in to add a comment
|
CRD has lots of problems at 1600x1062 resolution on Pixel 2 |
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 7647.84.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Platform: 7647.84.0 (Official Build) stable-channel panther Steps to reproduce the problem: 1. Using Pixel 2, set resolution to 1600x1062. 2. Use Chrome Remote Desktop to connect to remote host. 3. Notice weird artifacts that show up all over the screen, depending on the content. What is the expected behavior? No artifacts or other strange behavior. Note that all other resolutions from 1280x850 through 2560x1700 work flawlessly; just 1600x1062 is broken. Also note that I have extensive experience with the Pixel 1 and the ASUS chromebox. I use the chromebox every day without any problems, and this never happened on the Pixel 1 (although it's been months since I last used the Pixel 1). What went wrong? A bunch of strange behavior, including but not limited to: whole-screen flashes of color; colored blobs appearing in places where text is scrolling; "loops" where the last few screens cycle and no new input is recognized. When the "loops" occur, disconnecting and reconnecting CRD shows a completely black screen, which is cured only by rebooting the pixel. Additionally, the weird artifacts are not restricted to the CRD screen -- they affect other tabs and windows, and even the ChromeOS login screen. But they don't occur at all unless CRD is used at some point. Did this work before? No Chrome version: 48.0.2564.116 Channel: stable OS Version: 7647.84.0 Flash Version: Shockwave Flash 20.0 r0 I've been having this problem since I first got the Pixel 2, and have tried three different Pixel 2 machines, all with the same problem. I've reported on this internally at Google and can share additional information if necessary. This bug is 100% reproducible for me. I've been suffering with it for months, until this weekend when I discovered that it depended on the display resolution.
,
Mar 14 2016
,
Mar 14 2016
Can you please try disabling hardware decoding? Open chrome://flags/ and click disable under "Hardware-accelerated video decode". You will need to restart chrome after disabling that flag.
,
Mar 15 2016
I have done that and it has a small effect but does not eliminate the issue.
,
Mar 15 2016
,
Mar 15 2016
sergeyu@: may I temporarily assign to you for triage please? Looks like this happens without HW decode as well. Thanks.
,
Mar 15 2016
AJ, now that we know this is resolution-dependent, can you try to repro?
,
Mar 30 2016
What is the Host Platform and resolution? I was unable to reproduce this with a Windows 7, Linux or Mac Host.
,
Mar 30 2016
Host platform is goobuntu ubiquity instance running cinnamon. Resolution is set to auto-size according to client.. I've also had the same issue running on Google Compute Engine, running xfce. I can reproduce this reliably on either host platform.
,
Mar 30 2016
As a TVC I do not have access to an Ubiquity instance. Assigning to Anand for repro
,
Apr 20 2016
,
May 10 2016
,
Jun 3 2016
,
Jun 27 2016
I've also been seeing this on my Pixel 2 (Samus) for months - when I use Chrome Remote Desktop with my resolution set to 1600x1062 I get strange graphical glitches and corruption. You can see an example of this at the top of this screenshot: https://goto.google.com/crbug594816screenshot This is 100% reproducible for me when connecting to a Linux host using either Unity or XFCE as its desktop environment. The original reporter mentioned: >When the "loops" occur, disconnecting and reconnecting CRD shows a >completely black screen, which is cured only by rebooting the pixel. I've seen this as well with an additional data point - after the loops have occurred I'm unable to watch YouTube videos. Trying to view a YouTube video just results in me seeing a static black image where the video should be. For reference I'm on the stable channel with the following versions: Version 51.0.2704.103 (64-bit) Platform 8172.56.0 (Official Build) stable-channel samus Firmware Google_Samus.6300.174.0
,
Jul 25 2016
Issue 608035 has been merged into this issue.
,
Jul 25 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by cph@google.com
, Mar 14 2016