New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 784057 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 775202
Owner:
OOO until 2019-01-24
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Can't correctly render WebGL canvas to 2D canvas

Project Member Reported by gman@chromium.org, Nov 11 2017

Issue description

Chrome Version: 62.0.3202.89 (Official Build) (64-bit)
OS: macOS 10.13

What steps will reproduce the problem?
(1) Go to https://jsfiddle.net/greggman/qafe33bL/

What is the expected result?

There is a red square in the 2nd image

What happens instead?

There is no red square in the 2nd image or sometimes garbage

Works on Firefox


I noticed this issue because sometime in September vertexshaderart.com stopped being able to take screenshots for me when saving. It seems to be around the time as macOS 10.13 release. I tried to narrow it down but the issue is semi-intermittent. What happens is the WebGL canvas is normally 300x150 but when I take screenshot I increase it to 1200x672, re-render the scene, copy to canvas 2d, then the next render will move it back down to 300x150. If I change the copy resize to 301x151 the problem goes away or is intermittent. I've even seen garbage. If I turn off the depth test the problem also seems to go away even though I'm clearing the depth buffer and there is only 1 point being drawn.

 

Comment 1 by gman@chromium.org, Nov 11 2017

So screenshots to show errors
webgl-2-canvas-error-examples.png
461 KB View Download

Comment 2 by kbr@chromium.org, Nov 13 2017

Cc: zmo@chromium.org kainino@chromium.org
Mergedinto: 775202
Owner: kbr@chromium.org
Status: Duplicate (was: Untriaged)
Thanks for the report and your test case in https://github.com/KhronosGroup/WebGL/pull/2543 .

Based on the symptoms, I think it's the same basic issue as  Issue 775202 , so am duplicating this into the other report. This strongly appears to be a regression in the NVIDIA driver in 10.13.

Working on a standalone test case now. Will press Apple and NVIDIA for a fix.

Sign in to add a comment