search

oizma / angleproject

Automatically exported from code.google.com/p/angleproject
Other
0 stars 0 forks source link

Incorrect behavior on shader/program deletion #47

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.In windows, open Chrome (top-of-tree), and goto 
https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/tests/conforma
nce/object-deletion-behaviour.html, see the test failing.
2. If open Chrome with --use-gl=desktop flag, the test passes.
3.

What is the expected output? What do you see instead?

If a shader is attached to a program, or a program is the current bound one, 
deleteShader() or deleteProgram() should only mark the name as deleted, but the 
true deletion will be delayed.

However, current ANGLE implementation delete shader/program immediately upon 
deleteShader() or deleteProgram().

What version of the product are you using? On what operating system?

Top of tree chrome, in Windows Vista.

Please provide any additional information below.

Original issue reported on code.google.com by z...@google.com on 28 Sep 2010 at 2:57

GoogleCodeExporter commented 9 years ago 
Even if I force glIsShader() to return GL_TRUE, the test keeps saying it 
returned false. Also, when I create an application with the same sequence of 
function calls, they return the expected results.

So this doesn't appear to be an ANGLE bug.

Original comment by nicolas....@gmail.com on 11 Nov 2010 at 12:39

GoogleCodeExporter commented 9 years ago 
ANGLE's glIsShader() doesn't get called at all in this test. So I suspect that 
Chromium tries to keep track of the reference counts itself but doesn't take 
this special behavior into account.

Original comment by nicolas....@gmail.com on 17 Nov 2010 at 6:32

GoogleCodeExporter commented 9 years ago 
Zhenyao, could you please try again whether the test passes with desktop GL? 
I'm seeing the exact same tests fail when using --use-gl=desktop, which would 
mean this is definitely not an ANGLE issue. I'm using Chromium 9.0.578.0 
(65537) at the moment.

Original comment by nicolas....@gmail.com on 17 Nov 2010 at 10:00

GoogleCodeExporter commented 9 years ago 
Checked.  It's a chromium command buffer bug.  Sorry about the false alarm.

Original comment by z...@google.com on 17 Nov 2010 at 5:37

GoogleCodeExporter commented 9 years ago 
Thanks for checking.

closing this as invalid.

Original comment by dan...@transgaming.com on 17 Nov 2010 at 5:41