In my game engine I've noticed that GL might be leaking texture data. This issue is happening on a Nexus One (Adreno 200) running Android 2.2.
The following sequence of events happens during testing:
1) meminfo shows that the native heap is at size X
2) glGenTextures is called to generate a texture
3) glTexImage is called to specify texture data
4) meminfo shows that the native heap is at size Y (where Y-X is approximately the size of the texture data specified with glTexImage2D)
5) glDeleteTextures is called on the texture object created in 2)
6) meminfo shows that the native heap remains at around size Y. After letting the process run awhile longer the heap size still doesn't drop back down.
From the observations above, it looks like glDeleteTextures isn't actually freeing up the heap that was allocated when glTexImage2D is specified. I'm not sure if this is exactly the case, but I've ensured that no other allocations are being done between the glTexImage2D and glDeleteTextures call. Is there anything else that needs to be done to properly clean up texture data or is possible that there is a leak in the GL driver?