Comment 34 for bug 565981

Update on comment #33:

I managed to have a quick word with David Airlie, and he told me that the radeon driver does not report the pinned/pin/gtt values, so that's not an issue.

Here are some results from kernel 2.6.34-rc5 with the latest xorg-edgers packages [1]:

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

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
317861888 object bytes Xorg 23524 15108
319795200 object bytes Xorg 23524 15120
321794048 object bytes Xorg 23524 15120
323530752 object bytes Xorg 24292 15696
328589312 object bytes Xorg 24292 15696
329527296 object bytes Xorg 24292 15696
329826304 object bytes Xorg 23524 15120
331714560 object bytes Xorg 23524 15128
333737984 object bytes Xorg 23524 15168
335695872 object bytes Xorg 23524 15168

The results are almost identical to comment #33 - however, I am experiencing absolutely no slowdown or sluggishness despite the same high object count. Perhaps the bug is still present, but the driver or X server is more resistant to the GEM leak, somehow.

[1] current xorg-edgers X server version: 2:1.7.6.901+git20100413+server-1.7-nominations.e7ab6537-0ubuntu0sarvatt3. Upon inspecting the source, this build uses the same patches as mentioned in this bug's description, which probably means that the memory leak is to be expected. Why the slowdown does not occur is still a mystery, though.