Nicolai Hähnle wrote: > Hi, > > testing the r300-bufmgr has revealed that the driDestroyDrawable is never > called in very simple applications such as glxinfo or glxgears. This > obviously causes a number of memory leaks. Unfortunately, I don't really > understand that part of the code yet, but I have confirmed that the problem > also exists in git master. > > This is with the r300 driver, if it makes a difference.
I believe this problem has existed since day one. The problem is the client-side driver would need to get some sort of message from the X server when a window is destroyed. Otherwise, it's not clear when a window's DRI info can go away. I think there may be some "garbage collection" code that periodically checks if any of the window IDs previously passed to glXMakeCurrent() have gone away (by installing an X error hander and trying to "touch" the window ID). If a known window ID no longer exists on the server, the DRI info can be freed. I haven't looked at that stuff in quite a while so I'm not sure of the status of it. -Brian ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
