Hi All,
I am working with TI's OMAP3530 BSP with PoverVR and WinCE . I am writing an OpenGL based application where in i am trying to create texture objects. When i delete the texture i see that the whole memory allocated for texture is not freed.
if i log the available physical memory i could see that with every texture create and delete there is a significant loss of memory by 8 to 64 KB each time.
We are not sure why this memory leak is happening. Can you please help me to understand its architecture and the behaviour when we allocate and deallocate memory for creating and destroying the texture object.
Please see the memory status log :
Loading Texture data 1st time
###########################################################
MEMORY STATUS DISPLAY
###########################################################
1. MEMORY LOAD = 20 percent
2. TOTAL PHY MEM = 169385984 bytes
3. AVAIL PHY MEM = 136916992 bytes
4. TOTAL VIRTUAL MEM = 1073741824 bytes
5. AVAIL VIRTUAL MEM = 1063190528 bytes
#############################################################
Texture Loaded Successfully !!!
After Loading Textures
###########################################################
MEMORY STATUS DISPLAY
###########################################################
1. MEMORY LOAD = 25 percent
2. TOTAL PHY MEM = 169385984 bytes
3. AVAIL PHY MEM = 127725568 bytes
4. TOTAL VIRTUAL MEM = 1073741824 bytes
5. AVAIL VIRTUAL MEM = 1052311552 bytes
#############################################################
Texture deleted Successfully !!!
After Deleting Textures
###########################################################
MEMORY STATUS DISPLAY
###########################################################
1. MEMORY LOAD = 25 percent
2. TOTAL PHY MEM = 169385984 bytes
3. AVAIL PHY MEM = 127725568 bytes
4. TOTAL VIRTUAL MEM = 1073741824 bytes
5. AVAIL VIRTUAL MEM = 1052311552 bytes
#############################################################
Loading Texture data 2nd time
After Loading Textures
###########################################################
MEMORY STATUS DISPLAY
###########################################################
1. MEMORY LOAD = 27 percent
2. TOTAL PHY MEM = 169385984 bytes
3. AVAIL PHY MEM = 125308928 bytes
4. TOTAL VIRTUAL MEM = 1073741824 bytes
5. AVAIL VIRTUAL MEM = 1049493504 bytes
#############################################################
After Deleting Textures
###########################################################
MEMORY STATUS DISPLAY
###########################################################
1. MEMORY LOAD = 27 percent
2. TOTAL PHY MEM = 169385984 bytes
3. AVAIL PHY MEM = 125308928 bytes
4. TOTAL VIRTUAL MEM = 1073741824 bytes
5. AVAIL VIRTUAL MEM = 1049493504 bytes
#############################################################
LAST BUT NOT LEAST CONTEXT DESTROYED
###########################################################
MEMORY STATUS DISPLAY
###########################################################
1. MEMORY LOAD = 21 percent
2. TOTAL PHY MEM = 169385984 bytes
3. AVAIL PHY MEM = 134340608 bytes
4. TOTAL VIRTUAL MEM = 1073741824 bytes
5. AVAIL VIRTUAL MEM = 1059061760 bytes
#############################################################
This is a serious issue for us as we are using too many graphics in our actual implementation.
Hoping for a quick reply.
Regards,
Misbah