Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 2 of 2

Thread: textures not deleted?

  1. #1
    Intern Contributor
    Join Date
    Sep 2006
    Posts
    55

    textures not deleted?

    GLintercept produces this:
    GL Intercept Log. Version : 0.5 Compile Date: Dec 3 2005 Run on: Fri Feb 02 18:24:11 2007
    ================================================== =
    Diagnostic: Unknown function glGetQueryObjecti64vEXT being logged.
    Diagnostic: Unknown function glGetQueryObjectui64vEXT being logged.
    ImageManager:estructor - OpenGL id 1 is still active. (Image Memory leak?)
    ImageManager:estructor - OpenGL id 2 is still active. (Image Memory leak?)
    ================================================== =
    Log End.
    But also this:
    Code :
    glDeleteTextures(1,0xed6a50)
    glIsTexture(1)=false 
    glDeleteTextures(1,0xede3f8)
    glIsTexture(2)=false
    which logs the calls to delete them.
    I'm using only these 2 textures in my app.
    What is happening?

  2. #2
    Intern Contributor
    Join Date
    Sep 2006
    Posts
    55

    Re: textures not deleted?

    This GLintercept info seems to disappear magically now, after a recompile (which basically did not changed anything)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •