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

Issue 704165 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Mar 2017
Cc:
█ kbr@chromium.org
kainino@chromium.org
zmo@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

gl.clear() ignored after transform feedback

Reported by tshe...@gmail.com, Mar 22 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Open the test case HTML page in Chrome

What is the expected behavior?
Should animate a red point from the center of the screen toward the right.

What went wrong?
Smears the point across the screen, ignoring the gl.clear() call on line 186.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 56.0.2924.87  Channel: stable
OS Version: OS X 10.12.3
Flash Version: 

Running on the following hardware: Late 2014 mac mini, Intel Core i7 4578U, Intel Iris 5100

This does seem to work correctly in Chrome on Windows and Linux (on the machines I tested), and works in Firefox 52.0 on the same machine. I've attached a chrome://gpu dump of the affected machine. Seeing the following error in the logs: [658:775:0320/160738.630978:ERROR:gles2_cmd_decoder.cc(9520)] : [.Offscreen-For-WebGL-0x7fd0e6818000]GL ERROR :GL_INVALID_OPERATION : glDrawArrays: Source and destination textures of the draw are the same.
xform-feedback-clear.html
7.3 KB View Download
chrome-gpu-dump.txt
60.3 KB View Download

Comment 1 by tshe...@gmail.com, Mar 22 2017 

Just had a colleague test this on his Late 2013 Macbook Pro (OS X 10.12.3, Intel Core i7, Nvidia GeForce GT 750M) and he's seeing the same issue. So it looks like it's a general problem on OSX, rather than being related to a particular GPU.

chrome://gpu info for that machine is attached.
macbookpro-chromegpu.html
47.5 KB View Download

Comment 2 by zmo@chromium.org, Mar 22 2017

Cc: kbr@chromium.org zmo@chromium.org kainino@chromium.org
Status: Available (was: Unconfirmed)
Indeed, this works on Firefox on the same mac, and also works on my Linux in Chrome.

So it only fails on Chrome Mac.

Thanks for the test case - it helps a lot for us to fix the issue quickly.

Comment 3 by kainino@chromium.org, Mar 22 2017 

More datapoints:
Unable to repro on old beta (57.0.2987.74) or canary (59.0.3047.0) on 10.12.3 Intel, or on stable (57.0.2987.110) on 10.11.4 Intel, or on old beta (57.0.2987.88) on 10.12.4 beta AMD.

Comment 4 by zmo@chromium.org, Mar 22 2017 

To clarify: it fails for me on Stable, but succeed on Canary on the same Mac.

I guess that means it'x fixed at least on ToT.

Comment 5 by kbr@chromium.org, Mar 23 2017 

Is this reproducible with Chrome 57? The test runs correctly on my MBP with NVIDIA GeForce GT 750M (same as #1).
chrome-gpu.txt
6.1 KB View Download

Comment 6 by tshe...@gmail.com, Mar 23 2017 

Just tested in Chrome 57 and Canary on my machine (the Mac Mini), and it is fixed in both.

Comment 7 by kainino@chromium.org, Mar 23 2017

Status: Fixed (was: Available)
With 57 rolling out to stable already, this is fixed. Unfortunately I don't know what bug it was so I can't mark it duplicate.
►

Sign in to add a comment