Issue metadata
Sign in to add a comment
|
drawImage from webgl canvas to another canvas broken with CPU emulation of WebGL
Reported by
the1man...@gmail.com,
Sep 5
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: 1. disable hardware accelerated webgl 2. render something with webgl to one canvas (possibly offscreen) 3. use drawImage to copy part of that canvas to another canvas (without webgl context) What is the expected behavior? The copied section of the first canvas should be visible in the second canvas. What went wrong? nothing is copied. the second canvas remains blank. Note that it works fine when using hardware acceleration. Did this work before? Yes 67 maybe Does this work in other browsers? N/A Chrome version: 68.0.3440.106 Channel: stable OS Version: Flash Version: I have seen this on two separate end-users' computers (in different companies) both running some form of Windows Server. I am about 90% this is a regression.
,
Sep 6
Thanks for filing the issue! @Reporter: Could you please provide sample Test file/URL that reproduces the issue which help in further triaging it in better way. Note: Tentatively adding Blink>Canvas component to it. Thanks!
,
Sep 6
A code-pen is available here: https://codepen.io/anon/pen/Ooxgge (CPU rendering is only available on windows I believe, when you go to settings and disable hardware acceleration, or if your GPU was already blacklisted). The attached screenshot show it working, when it doesn't work the second bit is gone.
,
Sep 6
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 7
Unable to reproduce the issue on chrome reported version# 68.0.3440.106 and on latest stable# 69.0.3497.81 using Windows-10 with steps mentioned below: 1) Launched chrome reported version and disabled hardware acceleration from chrome://settings 2) Navigated to URL: https://codepen.io/anon/pen/Ooxgge, able to see "Source WebgGL canvas:" and "Destination canvas for drawImage:" Observations: Also tested the issue by Enabling the hardware acceleration from chrome://settings, able to see "Source WebgGL canvas:" and "Destination canvas for drawImage:" @Reporter: Please find the attached screencast for your reference for your reference and let us know if we missed anything in reproducing the issue, try to test this issue on latest stable# 69.0.3497.81 and let us know if the issue still persists. You can download latest chrome stable from URL: https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
Sep 7
Thanks for testing. I am away from work for a couple of weeks unfortunately but my colleague may investigate further in the meantime. If not I will update when I return as I was definitely seeing issues, but perhaps not on the very latest Chrome.
,
Sep 7
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 10
As per comment#6, awaiting the reply from reporter. Hence adding label Needs-Feedback. Thanks!
,
Sep 20
It does indeed seem to be working now on 69.0.3497.100 (64-bit)..which is great! (It definitely was broken on some released version of 68). Thanks for investigating and for a great browser ;) !!!!
,
Sep 20
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 21
As per comment# 9 from the reporter, issue seems to be working fine on latest stable# 69.0.3497.100, hence marking it as Won't fix. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Sep 6