Support forums

Graphics, Gaming, and VR forum Memory not free after glDeleteTextures call

Locked Locked
Replies 5 replies
Subscribers 136 subscribers
Views 6991 views
Users 0 members are here

Options

How was your experience today?

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Memory not free after glDeleteTextures call

Sebastien Baudouin over 11 years ago

Note: This was originally posted on 25th April 2013 at http://forums.arm.com

Hi ,

i'm using MALI-400 and its OpenGLES stack. Playing with textures, i discovered that the memory used by textures is not free just after glDeleteTextures call.
It seems also the same when using eglImages.
I would expect that just after the call to glDeleteTextures or eglDestroyImageKHR the memory used by the process using openGL decrease. But it is not the case.

Is there a possibility (API) to force the OpenGLES stack to free the memory and give it back to the system ?

Thanks for your help.

BR

Seb

Peter Harris over 11 years ago
Cancel
Up 0 Down

Cancel
Sebastien Baudouin over 11 years ago

Note: This was originally posted on 26th April 2013 at http://forums.arm.com

Hi,

thanks for looking at my post.

when i'm deleting the texture i'm sure it is the last context using it and also that any draw is finished (texture is no more used). I also tried to add a glFlush and again nothing changed. The memory is still used or at least assign to my thread. The problem i have is that i'm using lot of texture and a time by thread seems to own lot of memory while it is only using one texture.

I still don't understand why/how the texture memory is not freed ? May be the GL stack is having its own allocator and so the memory is kept by the GL stack even if my app is not using it. If it is the case then i'm wondering how to force it to release the memory.
BR

Seb
Cancel
Up 0 Down

Cancel
Peter Harris over 11 years ago

Note: This was originally posted on 26th April 2013 at http://forums.arm.com

Does the memory footprint drop after a glFinish (glFlush doesn't wait for rendering to complete, so the resource may still be referenced)?

Usual caveat - calling glFinish is normally "very slow" because it forces a pipeline drain of the whole rendering pipe - so it isn't something you want to do often.
Cancel
Up 0 Down

Cancel
Sebastien Baudouin over 11 years ago

Note: This was originally posted on 29th April 2013 at http://forums.arm.com

Hi,

i made a try adding gLFinish and it seems that the memory is not a freed for operation like:
- glDeleteTextures
- eglDestroyImageKHR
- glDeleteBuffers

Thanks for your help.

BR

Seb
Cancel
Up 0 Down

Cancel
Sebastien Baudouin over 11 years ago
Cancel
Up 0 Down

Cancel