search

pbfy0 / visvis

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

Textures seem not to be deleted properly #63

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
We found a memory leak in an app that creates a 2D texture about every second, 
and Destroy()'s the old ones.

I comfirmed that TextureObject.DestoryGl is called, which calls 
gl.glDeleteTextures(), so I don't understand what's happening. I should make a 
better test case and see what's going wrong.

Original issue reported on code.google.com by almar.klein@gmail.com on 29 Nov 2012 at 11:54

GoogleCodeExporter commented 9 years ago

Original comment by almar.klein@gmail.com on 29 Nov 2012 at 11:55

GoogleCodeExporter commented 9 years ago 
Mmm, the leak seems too small to really be the image data. Maybe it's more like 
a Python object witch cannot be cleaned up. Perhaps a circular reference?

Original comment by almar.klein@gmail.com on 11 Dec 2012 at 12:27

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision 3cc0061b5f58.

Original comment by almar.klein@gmail.com on 11 Dec 2012 at 1:58