GLIntercept messages ?

Started by
1 comment, last by kikosmalltalk 13 years, 5 months ago
Hi all

I implement a single demo on Dolphin Smalltalk.
I am using GLIntercept and this message returns:

InterceptDisplayList::CallLists - Calling non-existant list? 39
InterceptDisplayList::CallLists - Calling non-existant list? 49
InterceptDisplayList::CallLists - Calling non-existant list? 52
InterceptDisplayList::CallLists - Calling non-existant list? 27
DisplayListManager::RemoveData - Attempting to delete unknown DisplayList ID 96
GLDriver::DeleteOpenGLContext - Deleting current context 0x20000?


What does this mean?
Which is the error?


Advanced thanks

kiko
Advertisement
Are you trying to use GLIntercept as some kind of debugger? My experience with it is that you cannot always trust the logfile output.

Otherwise it would just mean what the error message says, you operate with display list that are not present.
Hi grey


Are you trying to use GLIntercept as some kind of debugger?

Yes.

My experience with it is that you cannot always trust the logfile output.

Why ?


I am experiencing a strange problem with textures

Look this topic:
http://www.opengl.org/discussion_boards/ubbthreads.php?ubb=showflat&topic=54591&gonew=1

I think it's a memory leak.
But I can not confirm .

This are other messages from GLIntercept:

DisplayListManager::RemoveData - Attempting to delete unknown DisplayList ID 95
DisplayListManager::RemoveData - Attempting to delete unknown DisplayList ID 96
GLDriver::DeleteOpenGLContext - Deleting current context 0x110000?
ImageManager::Destructor - OpenGL id 1 is still active. (Image Memory leak?)
ImageManager::Destructor - OpenGL id 2 is still active. (Image Memory leak?)
ImageManager::Destructor - OpenGL id 3 is still active. (Image Memory leak?)
ImageManager::Destructor - OpenGL id 4 is still active. (Image Memory leak?)
ImageManager::Destructor - OpenGL id 5 is still active. (Image Memory leak?)
ImageManager::Destructor - OpenGL id 6 is still active. (Image Memory leak?)
ImageManager::Destructor - OpenGL id 7 is still active. (Image Memory leak?)
ImageManager::Destructor - OpenGL id 8 is still active. (Image Memory leak?)
InterceptDisplayList::CallLists - Calling non-existant list? 39
InterceptDisplayList::CallLists - Calling non-existant list? 49



THIS :
ImageManager::Destructor - OpenGL id 1 is still active. (Image Memory leak?)

Means a memory leak? Or possible memory leak?

Look this image:
http://www.imagenserver.com.ar/show.php/17407_shell.JPG.html


When I select a new example , always call to glDeleteTextures and destroy the render context, but the VRAM is not cleaned !.


any idea ?

Advanced thanks

kiko

This topic is closed to new replies.

Advertisement