El miércoles, 7 de septiembre de 2005 19:27, Michel Dänzer escribió: > > Such behavior would be acceptable if X.org forgot old background > > images. But it doesn't. Try to successively load a series of > > background images, e.g. from the KDE wallpaper collection, and the > > memory occupied by Xorg will keep growing. > > First of all, verify using something like xrestop that it's not actually > a client leaking references to the wallpaper pixmaps. > > Even if that's ruled out, freeing memory that was allocated from the > heap can't always be returned to the system immediately because the heap > can only shrink down to the highest allocation still in use. If that's > the case, it should still be able to re-use a gap sometimes, especially > when you switch to a smaller wallpaper, in which case the memory usage > reported for the X server shouldn't increase. > > I'm curious as to which of these might apply to your situation, if any.
Hello, Siep. I have been testing with xrestop and Michel is right. My
machine
runs KDE 3.4.2 and X.Org 6.8.2.dfsg.1-6, and I cannot see any increment in
the memory usage in X. When I use a background, I see KDE Desktop process
going up in the comsumption list, but it does not surpass 5917 KB in any
case, even when I changed about twenty times my background desktop image.
I even saw Xorg process in a common 'top' with 115 MB of "resident
memory".
Another round of image switching did not changed Xorg's memory, until my
default setting: no background image. In this moment, Xorg even give me back
5 MB of memory, falling to 110 MB.
Is this true for you? If so, I would like to close this bug.
Best regards,
Ender.
--
So much to do, so little time...
-- Joker (Batman).
--
Debian developer
pgpFbFpguGHLC.pgp
Description: PGP signature
