Support forums

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

Locked Locked
Replies 5 replies
Subscribers 136 subscribers
Views 6992 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

Parents

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

Reply

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

Children

No data