Comment 36 for bug 565981

Revision history for this message
Conn O Griofa (psyke83) wrote :

Final test: kernel 2.6.34-rc5 + stock drivers + proposed X server update.

X server uptime: approximately 1 hour.

conn@nx9010:~$ glxinfo | grep "GLX version"
GLX version: 1.2

conn@nx9010:~$ pid=`pidof X` ; for t in `seq 1 10`; do eog /usr/share/backgrounds ; echo `grep "object bytes" /sys/kernel/debug/dri/0/gem_objects` `ps ocomm,vsz,rss $pid |grep X`; done
372658176 object bytes Xorg 32400 19844
374898688 object bytes Xorg 32400 19900
376623104 object bytes Xorg 32400 19840
378945536 object bytes Xorg 32400 19800
380846080 object bytes Xorg 32400 19712
382578688 object bytes Xorg 32400 19712
384847872 object bytes Xorg 32400 19712
386646016 object bytes Xorg 32400 19712
388882432 object bytes Xorg 32400 19712
390582272 object bytes Xorg 32400 18480

As you can see, the leak is still occurring. After reaching ~300MB in object bytes, the computer began to slow down due to excessive I/O and disk swapping, so applications were slower to load and respond; however, in periods of calm I/O activity, graphics performance is absolutely fine. I see no graphical slowdown whatsoever!

To summarise:
Kernel 2.6.32-21-generic + proposed X server from this bug report = memory leak, graphical slowdown
Kernel 2.6.32-21-generic + xorg-edgers packages = memory leak, graphical slowdown
Kernel 2.6.34-rc5 + proposed X server from this bug report = memory leak, no discernible graphical slowdown
Kernel 2.6.34-rc5 + xorg-edgers package = memory leak, no discernible graphical slowdown

In other words:
a) I get a memory leak in all cases, with or without the patched X server;
b) the newer kernel eliminates any graphical performance impact from the memory leak.

I'm not sure in what direction to proceed; since it seems that most people are seeing the bug fixed, perhaps this is a separate leak that's not related to 03_fedora_glx_versioning.diff and 04_fedora_glx14-swrast.diff. Shall I file a new bug, and if so, against what component?