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

Issue 619692 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Failed to get a valid WebGL2RenderingContext on Nvidia GTX 275 (341.95)

Reported by sturm.t...@gmail.com, Jun 13 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36

Steps to reproduce the problem:
1. Try to get a WebGL 2 context
2. The returned context is null
3. chrome://gpu -> ContextGroup::Initialize failed because maximum vertex output components is too small (56, should be 64).

What is the expected behavior?
Get a valid WebGL 2 Context

What went wrong?
The GL_MAX_VERTEX_OUTPUT_COMPONENTS query in context_group.cc returns a strange value of "56" instead of the real "64" vertex output components.

Did this work before? Yes I think the last version it did work was Chrome Stable 49 or 50

Chrome version: 51.0.2704.84  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

The GPU Caps Viewer returns the real value of "64" for the GL_MAX_VERTEX_OUTPUT_COMPONENTS query.
 
Components: Internals>GPU

Comment 2 by vmi...@chromium.org, Sep 30 2016

Cc: kbr@chromium.org zmo@chromium.org jmad...@chromium.org
Components: -Internals>GPU Internals>GPU>ANGLE Internals>GPU>WebGL
Labels: -Type-Bug-Regression Type-Bug
Removing Bug-Regression as WebGL 2 feature is pre-release.

Comment 3 by kbr@chromium.org, Sep 30 2016

Labels: -Pri-2 Needs-Feedback Pri-3
Sorry, I have no idea what's going on.

Please upgrade your graphics driver and provide about:gpu information from your system.

Comment 4 by ajuma@chromium.org, Dec 9 2016

Status: WontFix (was: Unconfirmed)
Closing given no response to #3.
Components: -Internals>GPU>WebGL Blink>WebGL

Sign in to add a comment