Canvas rendering twice on Lenovo
Reported by
becca.k...@pearson.com,
Mar 9 2017
|
||||||||||
Issue descriptionChrome Version: 57.0.2987.32 beta Chrome OS Version: 9202.18.0 beta-channel Chrome OS Platform: Lenovo N20p Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1)Open http://nextgen-styleguide.elasticbeanstalk.com/manipulatives-spinner.php (2)See that canvas is rendering incorrectly Expected Result: Canvas will only render once Actual Result: Canvas renders twice How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always Please provide any additional information below. Attach a screen shot or log if possible. This only happens on a Lenovo N20p. Have not been able to reproduce on Asus 300MA or Asus C100P For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Mar 20 2017
Could you please send us your GPU information? To do so, navigate to chrome://gpu, then copy the content of that page to a text file and attach it to this bug report. Thanks.
,
Mar 20 2017
,
Mar 21 2017
I have attached the GPU information. Please let me know if you need any additional information.
,
Mar 21 2017
Thank you for providing more feedback. Adding requester "junov@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
,
Apr 3 2017
Is there a particular CSS style that triggers this? Re-triaging as a compositing/paint bug. Rationale: canvas contents are correct, but not composited correctly.
,
Apr 4 2017
Given it's a specific machine that has the problem, over to the GPU folks to see if they have any insights. becca.kehl@, What are we looking for to know that it is rendering twice?
,
Apr 6 2017
I have attached a new code sample. The issue appears to be with lines 1058-1060. The shape is initialized and then moved and the shape appears both at the initialization location and the moved location. This does not happen on any other device or browser.
,
Apr 6 2017
Thank you for providing more feedback. Adding requester "schenney@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
,
Apr 7 2017
,
Apr 10 2017
Stephane, do we have this hardware in house? If yes, are you able to reproduce this?
,
Apr 10 2017
,
Apr 10 2017
Yes Chrome OS uses this hw, but we have a more recent mesa (17.x), and probably a more recent kernel (4.4). And we don't see that bug...
,
Apr 10 2017
I assume users can update to the latest?
,
Apr 10 2017
Yes, they will get updated eventually :) |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by dtapu...@chromium.org
, Mar 20 2017