• Locked Locked
  • Replies 5 replies
  • Subscribers 136 subscribers
  • Views 6993 views
  • Users 0 members are here
Options
Related
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
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
Parents
  • 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.
Reply
  • 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.
Children
No data