Issue metadata
Sign in to add a comment
|
Javscript console reports spurious warning of "no texture bound"
Reported by
eno...@onshape.com,
Mar 9 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.103 Safari/537.36 Steps to reproduce the problem: 1. navigate to: https://cad.onshape.com/documents/80749f31dad444bea395d55d/w/560ae7d829caddccfeed01e7/e/277e3887d03ad05fe2ce38da 2. log in (contact bug author privately if you need credentials) 3. open the javsacript console 4. observe this warning on each re-draw of the frame: "[.CommandBufferContext]RENDER WARNING: there is no texture bound to the unit 1" What is the expected behavior? I expect no warnings to show up. What went wrong? In previous versions of Chrome, no javascript warning is reported regarding texture binding. I put a break point in javascript right after the warning occurs and interrogated the GL state. It appears that there is a texture bound to unit 1, despite the warning. There do not appear to be any user-visible issues, despite the warning, which makes me think the warning is spurious. Did this work before? Yes Chrome 48.0.2564.103 Chrome version: 50.0.2661.18 Channel: dev OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 20.0 r0 Note: you may find other errors in the console in Chrome 50. This issue has been fix in Chrome 51 and is logged separately. See: https://bugs.chromium.org/p/chromium/issues/detail?id=591063 for more information.
,
Apr 28 2016
I dug a little further and discovered that there was no texture bound to the unit at the time of draw. In the shader that uses the texture, this is not a problem because the result of the sample is not used in that case. However, I can understand how in general having a null texture bound could be problematic, as there does not seem to be specified behavior for those samples. I "fixed" this on my end by ensuring there is always a texture bound, whether it ends up being used or not. I consider this issue resolved.
,
Apr 29 2016
OK. Assuming this is fully an application bug, closing as WontFix. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by erikc...@chromium.org
, Mar 15 2016Components: Internals>GPU
Status: Available (was: Unconfirmed)