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

Issue 625772 link

Starred by 2 users
Status: WontFix
Owner:
█ kbr@chromium.org
OOO until 2019-01-24
Closed: Sep 10
Cc:
kainino@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Compat



Sign in to add a comment

renderbufferStorageMultisample: multisampled float buffers not supported

Project Member Reported by mar...@unity3d.com, Jul 5 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2787.0 Safari/537.36

Example URL:

Steps to reproduce the problem:
render to floating point multisampled render target, then sample from render texture.

What is the expected behavior?
run in Firefox Nightly to see expected rendering

What went wrong?
image does not render correctly. Canary log these errors:

WebGL: INVALID_VALUE: renderbufferStorageMultisample: multisampled float buffers not supported
[.Offscreen-For-WebGL-0000018C84A0ADF0]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glClear: framebuffer incomplete
[.Offscreen-For-WebGL-0000018C84A0ADF0]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glDrawElements: framebuffer incomplete
[.Offscreen-For-WebGL-0000018C84A0ADF0]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glBlitFramebufferCHROMIUM: framebuffer incomplete

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? Yes 

Chrome version: 54.0.2787.0  Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

repro: https://oc.unity3d.com/index.php/s/VWZ0rhGFdSVazi4

Comment 1 by kbr@chromium.org, Jul 6 2016

Components: Blink>WebGL
Labels: -OS-Windows OS-All
Status: Available (was: Unconfirmed)
One point: this test case requires WebGL 2.0, i.e., the --enable-unsafe-es3-apis command line argument, or enabling it in about:flags.

The EXT_color_buffer_float WebGL wrapper extension in https://www.khronos.org/registry/webgl/extensions/EXT_color_buffer_float/ specifically disallows multisampled floating-point render targets. However, this is useful functionality, and the conformance test in https://www.khronos.org/registry/webgl/sdk/tests/conformance2/extensions/ext-color-buffer-float.html doesn't test this.

https://github.com/KhronosGroup/WebGL/issues/1845 has been filed to relax the EXT_color_buffer_float spec, and extend the conformance test.

Comment 2 by kbr@chromium.org, Sep 2 2016

Cc: kainino@chromium.org
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 4 2017

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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

Comment 4 by kainino@chromium.org, Sep 8 2017

Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
Still seems to repro.

Comment 5 by kbr@chromium.org, Sep 8 2017 

Really? The conformance tests were updated over a year ago to allow this case. Could the repro case be wrong?

Comment 6 by kainino@chromium.org, Sep 8 2017

Labels: Needs-Feedback
Actually it could just be a startup thing. There are 35 instances of
[.Offscreen-For-WebGL-0x2a908262ae00]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glClear: framebuffer incomplete
but glDrawElements and glBlitFramebufferCHROMIUM seem to be no longer producing errors.

There are similar errors in Firefox on my machine. But the rendering is actually still slightly different.

Marco: can you verify whether this is still an issue?
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

Owner: kbr@chromium.org
Status: WontFix (was: Untriaged)
The test case above runs successfully on 71.0.3548.0 (Official Build) canary (64-bit) on macOS. RFE https://github.com/KhronosGroup/WebGL/issues/1845 was fixed with the following pull requests:

https://github.com/KhronosGroup/WebGL/pull/1935
https://github.com/KhronosGroup/WebGL/pull/1946
https://github.com/KhronosGroup/WebGL/pull/1956

Closing as WontFix - no longer reproducible.

Comment 9 by mar...@unity3d.com, Sep 13 

Apologies for not checking earlier. The issue seem fixed. There is still one warning:
[.WebGL-000001E9FF8C9650] GL_INVALID_FRAMEBUFFER_OPERATION: Invalid framebuffer operation.

but I assume it's a problem on our side since Firefox also complains about it.
►

Sign in to add a comment