Petar,
You clearly implied that I was misinterpreting my results in the first
sentence of comment #37. In comment #59, I acknowledged that your system
appears not to have the same memory leak issue; as I said, your
allocation increases /and/ decreases, unlike my own. I asked for
evidence simply
Martin,
Although the initial feedback from most people seems to indicate that
the proposed update fixes the issue, I haven't seen anybody post output
that would positively confirm the leak as being fixed (in other words,
that the GEM object byte allocation is actually reducing when
applications
Petar Volkovski,
What you did in comment #51 is just another variation of the testcase in
the bug description that others have been performing (and that you
insist does not represent a memory leak).
Your output differs from mine in that the GEM allocation increases *and*
decreases. I have never
Unfortunately, this proposed X server update has not resolved the
problem on my system. I'm using a stock Ubuntu Lucid installation,
compiz enabled, and with the proposed X server update.
c...@nx9010:~$ lspci | grep VGA
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP
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]:
c...@nx9010:~$ glxinfo | grep
Using kernel 2.6.32-21-generic and xorg-edgers packages:
After just 10 minutes uptime the slowdown has occurred, with a lower
object bytes count than before. Here is the output at the point in which
the slowdown became noticeable:
c...@nx9010:~$ pid=`pidof X` ; for t in `seq 1 10`; do eog
Final test: kernel 2.6.34-rc5 + stock drivers + proposed X server
update.
X server uptime: approximately 1 hour.
c...@nx9010:~$ glxinfo | grep GLX version
GLX version: 1.2
c...@nx9010:~$ pid=`pidof X` ; for t in `seq 1 10`; do eog
/usr/share/backgrounds ; echo `grep object bytes
Peter Velkovski,
Thanks for the suggestion, but on my system - even if I close all
applications on the running X server - the GEM object bytes value
*never* decreases. Freeing the pagecache, dentries and inodes (as you
suggest) makes no difference at any point.
The only way to reduce the
Jeremy,
Unfortunately I can no longer do any testing due to the fact that the
laptop in question became physically damaged.
However, the bug may be invalid; I remember that there was a change to
the default mouse configuration which disabled touch-to-click at the
time I filed this bug (a fact I
9 matches
Mail list logo
