Issue metadata
Sign in to add a comment
|
Graphics corruption when using Chrome Remote Desktop on samus |
||||||||||||||||||||||||
Issue descriptionGoogle Chrome 50.0.2661.87 (Official Build) beta (64-bit) Revision 0 Platform 7978.62.0 (Official Build) beta-channel samus Blink 537.36 (@0) JavaScript V8 5.0.71.33 Flash 21.0.0.216-r2 User Agent Mozilla/5.0 (X11; CrOS x86_64 7978.62.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.87 Safari/537.36 What steps will reproduce the problem? (1) Use Ctrl-Shift-minus to increase screen resolution to 1600x1062 (2) Run Chrome Remote Desktop in a maximized window (3) Use it for a while. In particular, drag remote windows around Eventually you'll get into a state like the first screenshot. Sometimes the corruption extends into the window caption area (outside the remote desktop area). As in the second screenshot, sometimes the corruption appears on top of other windows -- see the green rectangle over the omnibox (this was with CRD minimized). Sometimes the corrupted area blinks. I've also seen grey rectangles (maybe 8x128 pixels) on the new tab page. I'm not sure if this is a CRD problem or a compositor/graphics problem, but I suspect the latter. wez, are you still on CRD? marcheu, any ideas here?
,
Apr 30 2016
My first thought was that this looks like a VP8 decoder barf - but IIUC you're seeing this without Chromoting involved at all, according to #1?
,
Apr 30 2016
Yes, in #1 I induced the problem by running CRD, but some corruption persisted even after I quit it. The magic combination seems to be: * Change screen resolution * Run CRD * Do something on the remote side that animates/moves a bunch of pixels Unfortunately I need to do all 3 of those things. :-(
,
May 3 2016
,
May 4 2016
jamescook@ -- can you provide some details on your CRD setup. - are you using your corp workstation to serve CRD? are you prompted to set up a 6-digit pin? - is your samus corp enrolled and are you prompted to enter the same 6-digit pin? I keep getting the message that the "Access Code is invalid" even though I have corp login and gnubby working on both machines.
,
May 4 2016
Yes, I'm using my corp Goobuntu workstation. I set up a 6-digit PIN a long time ago. I told the CRD app to remember it, so it doesn't prompt me anymore. My samus is corp enrolled.
,
May 4 2016
I can try to repro it at my desk tomorrow if you like.
,
May 13 2016
,
Jul 25 2016
,
Jul 25 2016
Sorry; de-duped the wrong way round. I think this should be the master bug, since it doesn't seem to be Chromoting-specific.
,
Jul 25 2016
,
Jan 28 2017
Does this still happen? Sorry I haven't looked at this lately
,
Jan 30 2017
I have not noticed this recently.
,
Jan 30 2017
I'm no longer able to reproduce this on Samus running: Version 55.0.2883.105 (64-bit) Platform 8872.76.0 (Official Build) stable-channel samus ARC Version 3617689 Firmware Google_Samus.6300.174.0
,
Jan 30 2017
This was still a problem last month but as of today I'm not seeing any issues. Happily going back to 1600x1062 resolution! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by jamescook@chromium.org
, Apr 29 201639.6 KB
39.6 KB View Download