Hi Experts,
I've run into an irritating problem.
After I load a picture with GLKTextureLoader, I can not free it from memory.
When I call glDeleteTextures(1,&texturename), nothing happens.
I use OpenglES2.0 on iOS5.1
Thanks in advance!
1
glDeleteTextures does not remove picture from memory
Started by Vorel512, May 09 2012 06:02 AM
6 replies to this topic
#4 Moderators - Reputation: 4635
Posted 09 May 2012 - 07:17 AM
Strictly speaking, the specification only says that, after deleting a texture object, the object is considered unused. It says nothing that internal resources has to be released. It is possible that internal resources are saved for future textures. If Instruments doesn't inspect the internal states of the OpenGL implementation, it is likely that it cannot differentiate between objects and internal resources.
The only way to determine if the texture is valid is to query the object handle with glIsTexture. But this does not reflect any internal resources which may be what Instruments is reporting.
The only way to determine if the texture is valid is to query the object handle with glIsTexture. But this does not reflect any internal resources which may be what Instruments is reporting.
#5 Members - Reputation: 280
Posted 09 May 2012 - 03:07 PM
well there is one thing you should try
I assume that you are probably deleting textures in dealloc method...
You should check if you still have working context (this is very important because otherwise you don't have working connection ) and delete textures before releasing context
"OpenGL functions do not work unless an OpenGL context has been created and is active within that thread. Thus, glGenTextures will do nothing before context creation, and glDeleteTextures will do nothing after context destruction."
for more info you should check http://www.opengl.org/wiki/Common_Mistakes part the object oriented Language problem
I assume that you are probably deleting textures in dealloc method...
You should check if you still have working context (this is very important because otherwise you don't have working connection ) and delete textures before releasing context
"OpenGL functions do not work unless an OpenGL context has been created and is active within that thread. Thus, glGenTextures will do nothing before context creation, and glDeleteTextures will do nothing after context destruction."
for more info you should check http://www.opengl.org/wiki/Common_Mistakes part the object oriented Language problem
#6 Members - Reputation: 3825
Posted 09 May 2012 - 05:19 PM
This is normal behaviour and is nothing to be worried about. The GL spec just specifies that the texture name is free for reuse and that the texture object has neither contents nor dimensionality. It says nothing whatsoever about the memory used for the object. GL implementations are free to keep the memory hanging around for subsequent reuse if necessary, to free it some arbitrary time later, or whatever the driver writer decides is the best behaviour.
Don't expect a glDeleteTextures call to behave like free () or delete in C/C++.
Don't expect a glDeleteTextures call to behave like free () or delete in C/C++.
It appears that the gentleman thought C++ was extremely difficult and he was overjoyed that the machine was absorbing it; he understood that good C++ is difficult but the best C++ is well-nigh unintelligible.
