New issue
Advanced search Search tips

Issue 711520 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Sep 10
Cc:
cwallez@chromium.org
geoffl...@chromium.org
jmad...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug-Regression



Sign in to add a comment

WebGLRenderingContext.getProgramInfoLog() returns unexpected value

Reported by glario52...@gmail.com, Apr 14 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Close all Chrome sessions 
2. Open new Chrome session
3. Go on an whatever application build with Three.js(https://threejs.org/examples/misc_controls_orbit.html)
4. Take a look to the browser console

What is the expected behavior?
A clean console with no errors and no warnings.

What went wrong?
An warning is thrown ->

THREE.WebGLProgram: gl.getProgramInfoLog()

caused by an unexpected value returned by WebGLRenderingContext.getProgramInfoLog( program ).

The value is a string formed by 4 empty spaces.

Did this work before? Yes 56.0.2924

Chrome version: 57.0.2987.133  Channel: stable
OS Version: 6.1 (Windows 7 Professional, 7601 - Service Pack 1)
Flash Version: 

The warning can be seen only on first load, after reloading the warning is gone.
log-warning.png
29.6 KB View Download

Comment 1 Deleted

Comment 2 by dglazkov@chromium.org, Apr 14 2017

Components: -Blink Blink>WebGL
Status: Untriaged (was: Unconfirmed)

Comment 3 by kainino@chromium.org, Apr 14 2017

Components: Internals>GPU>ANGLE
Status: Unconfirmed (was: Untriaged)
The return value of getProgramInfoLog is implementation dependent and applications should not depend on it having any particular value (I don't think an empty string is even guaranteed for no-error.) Maybe this is a Three.js bug?

Doesn't reproduce on Mac, so I'm guessing it's an ANGLE integration thing.

Comment 4 by zmo@chromium.org, Apr 14 2017

Cc: geoffl...@chromium.org cwallez@chromium.org jmad...@chromium.org
I agree with kainino.  Even on a successful compile/link, warnings could still be added in the log.

That said, returning an string with a few white spaces are less than perfect behavior.  If it's from ANGLE, we should avoid it.

The reason it only happens on the first time is Chrome cache the program so the second time it bypasses compile/link and simply loads the program from cache.

Comment 5 by kbr@chromium.org, Apr 14 2017

Labels: -Pri-2 Pri-3
Status: Available (was: Unconfirmed)
Agree that this is unspecified, but it would be nicer to not produce program info logs which are solely whitespace.

Comment 6 by glario52...@gmail.com, Sep 8 2017 

I think this is a problem with the graphics card because I disabled it to use only the processor for the rendering and the warning is gone.
Project Member

Comment 7 by sheriffbot@chromium.org, Sep 10

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by kbr@chromium.org, Sep 10

Status: WontFix (was: Untriaged)
Sorry, we aren't going to invest time in this area.
►

Sign in to add a comment