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

Issue 684309 link

Starred by 2 users
Status: WontFix
Owner:
zmo@chromium.org
Closed: Jan 2017
Cc:
█ kbr@chromium.org
kainino@chromium.org
nyerramilli@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Regression

Blocked on:
issue 662520


Sign in to add a comment

Regression : Unable to play “Black_rain” webgl demo, instead only black screen appears.

Reported by yfulgaon...@etouch.net, Jan 24 2017 
Chrome Version : 57.0.2987.8 (Official Build) 5716357fa4e765126615b02d3d6eb0da9b95a03a-refs/branch-heads/2987@{#54} 32/64 bit
OS : Mac(10.12.1, 10.11.6, 10.12), Windows(7,8,10), Linux 14.04

Test URL : http://demo.marpi.pl/archan/black_rain/

What steps will reproduce the problem?
1. Launch Chrome and navigate to above URL.
2. Wait until progress bar loads completely and observe the page.

Actual : Unable to play “Black_rain” webgl demo, instead only black screen appears.
Expected : Chrome should be able to play “Black_rain” webgl demo experiment.

This is a regression issue broken in ‘M-56’, below is the Manual Regression range and will soon update other info.
Good build : 56.0.2910.0
Bad build : 56.0.2911.0

Note : Able to run “Black_rain” webgl experiment in Firefox, Safari and Internet Explorer.
Expected_result.mov
8.2 MB Download
Actual_result.mov
2.5 MB Download

Comment 1 by kainino@chromium.org, Jan 24 2017

Blockedon: 662520
Labels: -OS-Linux -OS-Windows -OS-Mac OS-All
Owner: zmo@chromium.org
Status: Assigned (was: Unconfirmed)
Narrowed regression range via bisect-builds, to this one commit by zmo:

https://chromium.googlesource.com/chromium/src/+log/2b59401230ffbb3fc983c5fc3621a11bebabf873..951e541c5dcd9578b3b9653cdc1a6a8c6d5c03cb

The error is this:

Uncaught (in promise) TypeError: Failed to execute 'texImage2D' on 'WebGLRenderingContext': No function was found that matched the signature provided.

As apparent from the bisect, it looks like this is an intended behavior change. Assigning to zmo to make a decision, but this may be WontFix.

Comment 2 by nyerramilli@chromium.org, Jan 24 2017

Labels: ReleaseBlock-Stable
adding RBS label, please change if required.

Note: tried with other demos (https://www.chromeexperiments.com/webgl) - and they are working fine.
http://www.martin-laxenaire.fr/experiments/pewpewpew/
https://wizgrav.github.io/clubber/index.html

Comment 3 by zmo@chromium.org, Jan 24 2017

Cc: kainino@chromium.org kbr@chromium.org
Status: WontFix (was: Assigned)
The issue is in index.js:126891 where gl.texImage2D(gl.TEXTURE_2D, 0, gl.RGBA, gl.RGBA, gl.UNSIGNED_BYTE, source); is called and source is null, which isn't allowed because then we have no idea what is width/height.

Before Chrome 56, we generate an INVALID_VALUE in such case; since Chrome 56, due to a small spec change (null is no longer allowed in WebGL IDL) we throw an DOM exception instead, and that's why the content does not show.

Either case, your app is definitely doing something illegal even in pre Chrome 56. A correct app in general should not generate any GL errors.  You are doing something (that call to texImage2D) that doesn't matter to the app.  You should either fix that call with correct args, or remove it.

Chrome is working as intended.
►

Sign in to add a comment