Canvas doesn't work as a webgl texture in some instances
Reported by
david.ma...@kitware.com,
Oct 17
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Create a webgl or webgl2 canvas with a texture. 2. Create a large 2D canvas. 3. Draw a loaded Image to the 2D canvas. 4. Use the canvas as a texture for webgl. 5. For certain sizes, the texture doesn't show the image. Load the HTML file. If the bug occurs, the display will be blank. If the bug does not occur, you will see a colored checkerboard. What is the expected behavior? The webgl texture uses the canvas as a texture with the drawn image. What went wrong? The 2D canvas functions as if it is blank. It seems like drawing an image is done asynchronously and that only certain actions wait for the draw to complete. Using the canvas as a texture is not such an action. If you getImageData from the canvas before using it as a texture, it works. Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: This works in Firefox.
,
Oct 17
,
Oct 18
,
Oct 18
david.manthey@ Thanks for the issue... Unable to reproduce the issue on latest chrome version 70.0.3538.67 using Windows 10. Attaching screen-cast for reference. Steps: --------- 1. Launched chrome 2. Downloaded given html file and opened in new tab As we are able see the colored checkerboard. @Reporter: Could you please check the attached screen cast and please let us know if anything missed from our end and Could you please upgrade to latest chrome stable 70.0.3538.67, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel ". Let us know whether issue still persists. Thanks.!
,
Oct 18
I no longer see the issue on Chrome Version 70.0.3538.67 (Official Build) (64-bit). Thank you.
,
Oct 18
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
,
Oct 22
david.manthey@ Thanks for the update. Can you please confirm if this issue can be closed, as the issue is resolved in 70.0.3538.67 build? Thanks..
,
Oct 22
,
Oct 24
I no longer see the problem on Chrome 70.0.3538.67 on Windows. I couldn't replicate this on my version of Chrome on Ubuntu (I never saw the problem), but I think it should be confirmed that it is fixed in Ubuntu as well. My colleague who saw it on Ubuntu (69.0.3497.100) said his version wasn't offering the update to 70.x as of yesterday. I think it would be good to confirm it is fixed there.
,
Nov 1
My colleague confirms that Chrome 70 on his version of Ubuntu no longer has the bug. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by david.ma...@kitware.com
, Oct 17