I have a pb with the size of the Xserver growing when using gtkglext
The problem can be reproduces by the pixmap demo of gtkglext
(run the demo then change a lot the window size in order to free and allocate
many pixmaps). It seams that this pb does not appear on all the platforms/drivers.
But I had this pb on at least five machines with diff. graphic cards and drivers.
In order to check the pb I have tried a small program indep of gtkglext which
when running this program the X server grows and the memory is not released
when the program ends.
the program basilcally loops (1000 times) on
ourData->pm = XCreatePixmap(..)
glXMakeCurrent( ourData->dpy, ourData->glxpm, ourData->ctx );
glXMakeCurrent( ourData->dpy, None, NULL);
if glXMakeCurrent( ourData->dpy, ourData->glxpm, ourData->ctx ); is commented
the memory leak does not appear if glXMakeCurrent( ourData->dpy, ourData->glxpm,
ourData->ctx ) is present it seams that XFreePixmap does not do its job.
Maybe I'm doing something wrong.
Created attachment 6213 [details]
Please post your xorg.conf and your xorg log.
Created attachment 6407 [details]
xorg.conf on a Dell GX620
Created attachment 6408 [details]
Are you also experiencing this with a more current version of the xorg-server?
(In reply to comment #5)
> Are you also experiencing this with a more current version of the xorg-server?
Yes I think I have the same pb on a laptop with Fedora Core 5 and
a more current version of the xorg-server.
Adding to 7.2 tracker to see if we can hunt this down.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Move to 7.3 tracker.
(In reply to comment #9)
> Move to 7.3 tracker.
Since the bug report, I have now a Fedora Core 7 release
and now the program crashes ! trying to discover the carsh
origin I have detected that the glxpixmap demo of Mesa
was crashing the same way: Mesa-7.0/progs/xdemos/glxpixmap.c
Error of failed request: GLXBadContext
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 30
Current serial number in output stream: 30
this happens on a Dell GX620 with the Intel driver.
It works fine on an other machine with nvidia driver (proprietary one).
This bug is really blocking for me !
There was a GLX pixmap leak fix in xserver 1.6.1, though I'm not sure it's the same problem. You may wanna give it a shot though.
closing as probably fixed due to feedback timeout -- if this problem still occurs, please reopen. thanks.
As far as I can understand, the bug is not fixed.
But the formulation has maybe evolved.
For example, the basic mesa demo with pixmaps fail on intel graphics and
my application still crashes on intel graphics (works on nvidia) when I
try to use opengl with pixmap rendering.
Regularly some people are talking about problems with Opengl
with pixmaps rendering on the gtkglext mailing list.
I will try to update the demo.
(In reply to comment #14)
> For example, the basic mesa demo with pixmaps fail on intel graphics and
> my application still crashes on intel graphics (works on nvidia) when I
> try to use opengl with pixmap rendering.
That's not the same as a memory leak, so it would need to be tracked separately. However, this should be fixed in Mesa Git and the upcoming 7.5.1 release.
If you're still seeing leaks with at least xserver 1.6.x and Mesa 7.5.x, please try to get more information about them, e.g. with valgrind or Odin (http://cgit.freedesktop.org/~ickle/odin/).
Closing again, as it looks like the leak originally reported is fixed. Additionally, the bug was reopened because glx pixmaps crashes, but the glxgear_pixmap demo from mesa work just fine here. If there still is a problem with glx pixmaps and you have a test case that demonstrates this, please file a new bug and attach the test case there. Thanks.