Jump to content
  • Advertisement
Sign in to follow this  
Vorel512

OpenGL glDeleteTextures does not remove picture from memory

This topic is 2259 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

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!

Share this post


Link to post
Share on other sites
Advertisement
What do you mean with "nothing happens", how do you observe that "nothing happens" and what do you expect to happen?

Share this post


Link to post
Share on other sites
In Instruments I do not see any memory drop.
Even if I remove a lot of textures.

Maybe it is because I use automatic reference counting.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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++.

Share this post


Link to post
Share on other sites
try to use again that texture. You'll probably see no texture.

And then try to load a new texture with same size, probably you will notice no memory usage increase.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!