Bug#606604: xorg: High memory usage when setting "radeon, modeset=0", in /etc/modprobe.d/radeon-kms.conf
On Mit, 2010-12-15 at 11:42 +0600, Александр Е. Ивлев wrote:
>
> This time I used htop and xrestop for xorg pixmaps monitoring.
Which value(s) exactly are you looking at in htop?
> First I ran the system and made measurements.
> Then I ran a few X applications and made measurements.
> And in the end I closed applications, and made measurements.
>
> Here are the results:
>
> kms=1 --------------------------------------------------------
>
> htop: 21184K
> xrestop:
> Pixmaps: 11641K Other: 45K All: 11687K
>
> htop: 29408K
> xrestop:
> Pixmaps: 32658K Other: 96K All: 32755K
>
> htop: 28032K
> xrestop:
> Pixmaps: 13348K Other: 47K All: 13395K
>
> kms=0 --------------------------------------------------------
>
> htop: 43376K
> xrestop:
> Pixmaps: 12577K Other: 45K All: 12623K
>
> htop: 60688K and continues to grow ???
> xrestop:
> Pixmaps: 35481K Other: 94K All: 35575K
>
> htop: 59864K
> xrestop:
> Pixmaps: 14284K Other: 47K All: 14331K
Assuming the memory is actually used by the X server process, can you
try to find out where it's allocated from? Running the X server
(preferably with xserver-xorg-core-dbg installed) in valgrind
--leak-check=full might be a start, though something like odin
(http://cgit.freedesktop.org/~ickle/odin) or memprof may be necessary if
the memory is freed during X server shutdown.
--
Earthling Michel Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
Reply to: