Cleanup shader destruction path leading to glDeleteShader call |
|||
Issue descriptionshader_manager.cc has a deletion path which is not symmetric to program_manager.cc . And functions managing the use count and marking for deletion do more than what they are named for, like calling glDeleteShader indirectly. It was noticed when debugging a shader leak in upstream mesa and following the code from chromium side.
,
Aug 10
Is there more work needed or is this done?
,
Aug 13
This is done, thanks. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, May 24 2018