Issue metadata
Sign in to add a comment
|
Messed up frame with wrong position of characters and black areas on Code Search |
||||||||||||||||||||||||
Issue descriptionChrome Version: 62.0.3198.0 (Official Build) dev (64-bit) OS: Ubuntu 14.04 derivative What steps will reproduce the problem? (1) Search something on cs.chromium.org (2) Scrolling down on the code What is the expected result? Clean code is shown What happens instead? Messed up (see attached screenshot) For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Sep 1 2017
,
Sep 1 2017
Tested on latest Stable #60.0.3112.113 and Dev #62.0.3198.0 on Ubuntu 14.04, Windows 7 and Mac 10.12.6 and unable to reproduce the issue mentioned. Please refer the screencast attached. @shimazu -- Could you please try by removing the extensions and creating a new profile to verify if the issue still persists. Please let us know if we have missed anything. Thanks in advance.
,
Sep 3 2017
I see similar in crosh/shell on dev. Also wasn't there on stable. Version 62.0.3198.0 (Official Build) dev (32-bit) Platform 9887.0.0 (Official Build) dev-channel veyron_minnie Firmware Google_Veyron_Minnie.6588.237.0
,
Sep 5 2017
I could reproduce it with using another profile by --user-data-dir and guest mode (please see attached screenshot). Ah, I found the position of scrolling bar might be wrong when the screen goes bad. Will it be a clue for the issue?
,
Sep 5 2017
,
Sep 5 2017
Thank you for providing more feedback. Adding requester "pnangunoori@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
,
Sep 5 2017
Seeing it too since the last Dev channel update (62.0.3198.0). +gpu compositing folks.
,
Sep 5 2017
+kylechar to see if this is a surface reference issue. If not we can pass along to raster folks, as necessary.
,
Sep 5 2017
This isn't something related to surface references. We're not missing any viz::Surface contents in the screenshots. I would say this is a raster problem, but I'm not very familiar with raster. The log errors are a bit weird. There are a lot of failed X11 commands, mostly request_code 4 which I'm pretty sure is from XDestroyWindow()? Maybe they're unrelated, but I don't know why we would be trying to destroy an XWindow so many times. +piman, enne and vmpstr for triage help
,
Sep 5 2017
,
Sep 5 2017
We've been seeing a lot of this. I think it's a duplicate.
,
Sep 5 2017
I think this is something that skobes fixed recently.
,
Sep 5 2017
,
Sep 6 2017
Issue 762348 has been merged into this issue. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by shimazu@chromium.org
, Sep 1 2017