On 07.01.2014 22:36, Yves-Alexis Perez wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Tue, Jan 07, 2014 at 09:49:48PM +0100, Zlatko Calusic wrote:
Package: lightdm-gtk-greeter
Version: 1.6.1-4
Severity: normal

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root     27352  0.2  0.8 143040 36104 tty7     Ss+  17:25   0:22 /usr/bin/X :0 
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
lightdm  27370  0.4  0.6 401064 26404 ?        Ssl  17:25   0:45 
/usr/sbin/lightdm-gtk-greeter

An hour later...

root     27352  0.2  0.9 145452 38476 tty7     Ss+  17:25   0:30 /usr/bin/X :0 
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
lightdm  27370  0.4  0.6 402252 27460 ?        Ssl  17:25   1:01 
/usr/sbin/lightdm-gtk-greeter

That's about +1MB RSS per hour for lightdm-gtk-greeter, and about +2MB RSS per
hour for X. Last time I went on a 2 week vacation, when I returned greeter had
half a gig RSS. Forgot to screenshot it.

To make matters worse, X is not releasing allocated memory after login. It
persists until the end of the session, when it is finally restarted.

I tried reverting to the default theme (Adwaita), but it doesn't change a
thing (still leaks).

Finally, CPU usage is also a bit problematic. I suspect it is somehow connected
to the memory leak. Eventhough 0.2 - 0.4% CPU is not much, it's still unexpected
for a display manager. Not to mention that it doesn't allow CPU on an otherwise
dormant machine to go to deep sleep and probably wastes a lot of power.

Can you provide a valgrind log? See
http://valgrind.org/docs/manual/quick-start.html


I replaced `start-stop-daemon --start --quiet --pidfile /var/run/lightdm.pid --name lightdm --exec $DAEMON -b|| echo -n " already running"' in /etc/init.d/lightdm with `valgrind --leak-check=yes $DAEMON', fired up screen and run `/etc/init.d/lightdm start >out 2>err' in it. Will send you the files in about an hour, after I ctrl-C it.

I hope that's what you need? Never run valgrind before. :P

--
Zlatko


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to