Debian Bug report logs -
#734526
lightdm-gtk-greeter: leaking memory
Reported by: Zlatko Calusic <zcalusic@bitsync.net>
Date: Tue, 7 Jan 2014 21:03:01 UTC
Severity: normal
Found in version lightdm-gtk-greeter/1.6.1-4
Fixed in version 1.8.2-1
Done: Yves-Alexis Perez <corsac@debian.org>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Tue, 07 Jan 2014 21:03:06 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
New Bug report received and forwarded. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Tue, 07 Jan 2014 21:03:06 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
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.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.13.0-rc6+ (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages lightdm-gtk-greeter depends on:
ii libc6 2.17-97
ii libcairo2 1.12.16-2
ii libgdk-pixbuf2.0-0 2.28.2-1+b1
ii libglib2.0-0 2.36.4-1
ii libgtk-3-0 3.8.6-1
ii liblightdm-gobject-1-0 1.8.5-3
ii libx11-6 2:1.6.2-1
Versions of packages lightdm-gtk-greeter recommends:
ii desktop-base 7.0.3
ii gnome-icon-theme-symbolic 3.10.1-1
ii gnome-themes-standard 3.8.4-1
ii policykit-1 0.105-4
lightdm-gtk-greeter suggests no packages.
-- Configuration Files:
/etc/lightdm/lightdm-gtk-greeter.conf changed:
[greeter]
background=/usr/share/images/desktop-base/login-background.svg
theme-name=Clearlooks-Phenix
xft-antialias=true
xft-hintstyle=hintfull
xft-rgba=rgb
show-clock=true
-- no debconf information
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Tue, 07 Jan 2014 21:39:09 GMT) (full text, mbox, link).
Acknowledgement sent
to Yves-Alexis Perez <corsac@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Tue, 07 Jan 2014 21:39:09 GMT) (full text, mbox, link).
Message #10 received at 734526@bugs.debian.org (full text, mbox, reply):
-----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
Regards,
- --
Yves-Alexis Perez
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBCgAGBQJSzHM+AAoJEG3bU/KmdcClQpUH/3rxN9WXeu97WazgsXdlHi1+
v/p6txTuAXZYWona/Ehka/8JYYf6W62Q6bgFSwPCVMagY5IGZYzWjkD3DBGtDn42
O91WCJ844QkAztqYOqqpUEFWuUmD7dafosaF5RFu5ZmnGfjN8CLrkv+kK7B9R0/F
IoG1rsrnTbzYE/Xx+yviwLG3vkBs3iK3YWmoAnYYcJM7nxyYAQmosjihSa2MEqzP
XCGBz1DDo3kqjC37aoHofnY0KFQC7CgYgNsxwEtioghINJRZ1jcUBwS00uRmMvgA
passHc0CIizTJQRtK03gv7NxL2gDtEifvNH1RmDJ8deO99NduoaxFoFoc9cSI78=
=aFK8
-----END PGP SIGNATURE-----
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Tue, 07 Jan 2014 23:03:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Tue, 07 Jan 2014 23:03:04 GMT) (full text, mbox, link).
Message #15 received at 734526@bugs.debian.org (full text, mbox, reply):
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
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 08 Jan 2014 00:09:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 08 Jan 2014 00:09:04 GMT) (full text, mbox, link).
Message #20 received at 734526@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On 07.01.2014 23:52, Zlatko Calusic wrote:
>
> 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
>
Log attached. Though, I'm not sure this will be helpful. This is
valgrind log of lightdm daemon, but it's not daemon that is leaking, but
gtk-greeter! I don't know how to run valgrind on gtk-greeter, which is
started internally by lightdm. Please instruct.
--
Zlatko
[valgrind.log.gz (application/gzip, attachment)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 08 Jan 2014 00:21:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 08 Jan 2014 00:21:04 GMT) (full text, mbox, link).
Message #25 received at 734526@bugs.debian.org (full text, mbox, reply):
On 08.01.2014 01:07, Zlatko Calusic wrote:
> On 07.01.2014 23:52, Zlatko Calusic wrote:
>>
>> 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
>>
>
> Log attached. Though, I'm not sure this will be helpful. This is
> valgrind log of lightdm daemon, but it's not daemon that is leaking, but
> gtk-greeter! I don't know how to run valgrind on gtk-greeter, which is
> started internally by lightdm. Please instruct.
>
Actually, I know! I replaced lightdm-gtk-greeter binary with a shell
script wrapper which will invoke real binary under valgrind. Another hour...
--
Zlatko
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 08 Jan 2014 01:39:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 08 Jan 2014 01:39:05 GMT) (full text, mbox, link).
Message #30 received at 734526@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On 08.01.2014 01:19, Zlatko Calusic wrote:
> On 08.01.2014 01:07, Zlatko Calusic wrote:
>> On 07.01.2014 23:52, Zlatko Calusic wrote:
>>>
>>> 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
>>>
>>
>> Log attached. Though, I'm not sure this will be helpful. This is
>> valgrind log of lightdm daemon, but it's not daemon that is leaking, but
>> gtk-greeter! I don't know how to run valgrind on gtk-greeter, which is
>> started internally by lightdm. Please instruct.
>>
>
> Actually, I know! I replaced lightdm-gtk-greeter binary with a shell
> script wrapper which will invoke real binary under valgrind. Another
> hour...
>
Attached...
--
Zlatko
[valgrind.log.gz (application/gzip, attachment)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 08 Jan 2014 09:21:07 GMT) (full text, mbox, link).
Acknowledgement sent
to Yves-Alexis Perez <corsac@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 08 Jan 2014 09:21:07 GMT) (full text, mbox, link).
Message #35 received at 734526@bugs.debian.org (full text, mbox, reply):
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Wed, Jan 08, 2014 at 02:34:43AM +0100, Zlatko Calusic wrote:
> On 08.01.2014 01:19, Zlatko Calusic wrote:
> >On 08.01.2014 01:07, Zlatko Calusic wrote:
> >>On 07.01.2014 23:52, Zlatko Calusic wrote:
> >>>
> >>>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
> >>>
> >>
> >>Log attached. Though, I'm not sure this will be helpful. This is
> >>valgrind log of lightdm daemon, but it's not daemon that is leaking, but
> >>gtk-greeter! I don't know how to run valgrind on gtk-greeter, which is
> >>started internally by lightdm. Please instruct.
> >>
> >
> >Actually, I know! I replaced lightdm-gtk-greeter binary with a shell
> >script wrapper which will invoke real binary under valgrind. Another
> >hour...
> >
>
> Attached...
Thanks, I'll take a look with upstream and see if we can find something.
Regards,
- --
Yves-Alexis Perez
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJSzRfjAAoJEG3bU/KmdcClRzsH+wdYxtErFwZu0fQJawDEZKMO
7YmHD/hcl6eNMeumWRqNIyCYUkaCvJkhFL2HPRlO+BWnWzZG78Y1vqWUyn5oUTEf
dC180uJ+Qv+WIFp26bhvh2uMbY3z349qAdKWL2/0jugUYk4n8hEz3BbQv8dwy/Ps
0Jx9ao8ywSBOOPWSiXcsbbCEyr++uYkPvZxB/zHOVXuN/5Q5vzBPjPpffHHfjBnL
Bv0kwxPe3VCUt1MDI/R9FrPe8mg6dF8fxFxhXyqWZ5piUkk5VZ+F+0OQ8x0EmnZD
AwvIyl/bBbiyc0+B+KIRHwzNSmcPvdcVbzgMQJdtWbh6E/ONlxP/evPBtZQzRjY=
=YrPG
-----END PGP SIGNATURE-----
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 08 Jan 2014 10:30:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 08 Jan 2014 10:30:05 GMT) (full text, mbox, link).
Message #40 received at 734526@bugs.debian.org (full text, mbox, reply):
On 08.01.2014 10:18, Yves-Alexis Perez wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On Wed, Jan 08, 2014 at 02:34:43AM +0100, Zlatko Calusic wrote:
>> On 08.01.2014 01:19, Zlatko Calusic wrote:
>>> On 08.01.2014 01:07, Zlatko Calusic wrote:
>>>> On 07.01.2014 23:52, Zlatko Calusic wrote:
>>>>>
>>>>> 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
>>>>>
>>>>
>>>> Log attached. Though, I'm not sure this will be helpful. This is
>>>> valgrind log of lightdm daemon, but it's not daemon that is leaking, but
>>>> gtk-greeter! I don't know how to run valgrind on gtk-greeter, which is
>>>> started internally by lightdm. Please instruct.
>>>>
>>>
>>> Actually, I know! I replaced lightdm-gtk-greeter binary with a shell
>>> script wrapper which will invoke real binary under valgrind. Another
>>> hour...
>>>
>>
>> Attached...
>
> Thanks, I'll take a look with upstream and see if we can find something.
>
Thank you Yves-Alexis for good work!
--
Zlatko
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 08 Jan 2014 10:45:14 GMT) (full text, mbox, link).
Acknowledgement sent
to Yves-Alexis Perez <corsac@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 08 Jan 2014 10:45:14 GMT) (full text, mbox, link).
Message #45 received at 734526@bugs.debian.org (full text, mbox, reply):
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Wed, Jan 08, 2014 at 11:27:52AM +0100, Zlatko Calusic wrote:
> >Thanks, I'll take a look with upstream and see if we can find something.
> Thank you Yves-Alexis for good work!
It seems that some leaks were fixed in 1.7.0. Can you try the one in
experimental?
Regards,
- --
Yves-Alexis Perez
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJSzSsIAAoJEG3bU/KmdcClBWQH/j8LM7bvGplCuRjTrYKbPufu
tZi6Gxa19PlKlXg5wlKdYdJz0JnPlHnIoh2peMhMY0OHp3mmdXetknSWF3ufPMs4
+3QYql3uBJaE+BSx/IJczlwWiszPQdS9Nee8ne3k0FZ7uVFswByvBOYN2Nk9B5jP
0ytOQG6XH4p3iyn9J7PU521X0gpNU5L7j74YTq/VRfpbwOqUKes1KpaeBoK38kxU
hTThU0atZyG+FDAzvRfOudA5tTFyGqbZJ4qEG7kaVYPbSHWv7zosYjg1Z0jqxohP
MRLabNSdkxKn9BbtlvWsTeOiGq64qu1qoJKaWc3R3tyPn25bNrR1lFisD39n9UU=
=lk20
-----END PGP SIGNATURE-----
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 08 Jan 2014 11:03:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 08 Jan 2014 11:03:08 GMT) (full text, mbox, link).
Message #50 received at 734526@bugs.debian.org (full text, mbox, reply):
On 08.01.2014 11:40, Yves-Alexis Perez wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On Wed, Jan 08, 2014 at 11:27:52AM +0100, Zlatko Calusic wrote:
>>> Thanks, I'll take a look with upstream and see if we can find something.
>> Thank you Yves-Alexis for good work!
>
> It seems that some leaks were fixed in 1.7.0. Can you try the one in
> experimental?
>
Sure thing. Wasn't even aware there was an experimental version. Will
test it later today and report my findings.
--
Zlatko
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 08 Jan 2014 21:57:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 08 Jan 2014 21:57:05 GMT) (full text, mbox, link).
Message #55 received at 734526@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On 08.01.2014 12:00, Zlatko Calusic wrote:
> On 08.01.2014 11:40, Yves-Alexis Perez wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> On Wed, Jan 08, 2014 at 11:27:52AM +0100, Zlatko Calusic wrote:
>>>> Thanks, I'll take a look with upstream and see if we can find
>>>> something.
>>> Thank you Yves-Alexis for good work!
>>
>> It seems that some leaks were fixed in 1.7.0. Can you try the one in
>> experimental?
>>
>
> Sure thing. Wasn't even aware there was an experimental version. Will
> test it later today and report my findings.
>
Valgrind log from 2 hour run of 1.7.0 with stock configuration for the
sake of testing. Leaks still there, I'm afraid.
--
Zlatko
[valgrind.log.gz (application/gzip, attachment)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Thu, 09 Jan 2014 06:27:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Alistair Buxton <a.j.buxton@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Thu, 09 Jan 2014 06:27:05 GMT) (full text, mbox, link).
Message #60 received at 734526@bugs.debian.org (full text, mbox, reply):
Hi,
Please install debug symbols for glib and gdk and then rerun valgrind with:
--leak-check=full --show-leak-kinds=all
Also please note lightdm-gtk-greeter is expected to leak exactly one
X11 pixmap which contains the user's wallpaper and sticks around after
the greeter exits.
--
Alistair Buxton
a.j.buxton@gmail.com
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Thu, 09 Jan 2014 06:54:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Yves-Alexis Perez <corsac@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Thu, 09 Jan 2014 06:54:05 GMT) (full text, mbox, link).
Message #65 received at 734526@bugs.debian.org (full text, mbox, reply):
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Thu, Jan 09, 2014 at 06:23:46AM +0000, Alistair Buxton wrote:
> Hi,
>
> Please install debug symbols for glib and gdk and then rerun valgrind with:
> --leak-check=full --show-leak-kinds=all
In order to do that on Debian, you'll need libglib2.0-0-dbg and
libgtk-3-0-dbg.
Regards,
- --
Yves-Alexis Perez
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBCgAGBQJSzkXMAAoJEG3bU/KmdcClFDMIAK3HClQV0Xbaz0G5baQqi0Fj
s/BiUMHh0EQt2K3ocAmYPMbirZBKtTtSDc12YPxv97SIjoRZlTn85NXaH956qlWu
JVrt60NGzEcrxHKnuyuKfEayq1sRvxvP/lQtisk9m7Dr4tdqhBOxm5+iSc3V4nFz
F0DHP54Ork4hxbDMMCJv6bM00eRTVk9LvOdM/OMgEp/0TCl8Blw+gvAQjjppCswg
J9XdP8c7oiWqG6T2CepnF/GdDZFptI1rsQrsjyAmA9cJHayESyUXvEx3WWnbzhyy
dlW8LKtN4b3msofbUfc34X3Q0os8F0Sjqn1C1FmaYymnqxW+shxvhiMbVqHhAk4=
=CGyl
-----END PGP SIGNATURE-----
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Thu, 09 Jan 2014 17:39:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Thu, 09 Jan 2014 17:39:05 GMT) (full text, mbox, link).
Message #70 received at 734526@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On 09.01.2014 07:46, Yves-Alexis Perez wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On Thu, Jan 09, 2014 at 06:23:46AM +0000, Alistair Buxton wrote:
>> Hi,
>>
>> Please install debug symbols for glib and gdk and then rerun valgrind with:
>> --leak-check=full --show-leak-kinds=all
>
> In order to do that on Debian, you'll need libglib2.0-0-dbg and
> libgtk-3-0-dbg.
>
Packages with symbols installed, new valgrind log attached. Still
default config, run greeter for about 7-8 hours.
Regards,
--
Zlatko
[valgrind.log.gz (application/gzip, attachment)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Thu, 09 Jan 2014 18:54:15 GMT) (full text, mbox, link).
Acknowledgement sent
to Alistair Buxton <a.j.buxton@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Thu, 09 Jan 2014 18:54:15 GMT) (full text, mbox, link).
Message #75 received at 734526@bugs.debian.org (full text, mbox, reply):
Thanks.
==18357== 4,419,486 bytes in 245,527 blocks are definitely lost in
loss record 6,586 of 6,587
==18357== at 0x4C294A0: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==18357== by 0x6A7FEF7: __vasprintf_chk (vasprintf_chk.c:80)
==18357== by 0x5FA0A4B: g_vasprintf (stdio2.h:210)
==18357== by 0x5F7ED5F: g_strdup_vprintf (gstrfuncs.c:517)
==18357== by 0x5F7EDFB: g_strdup_printf (gstrfuncs.c:543)
==18357== by 0x112186: ??? (in /usr/sbin/lightdm-gtk-greeter.real)
==18357== by 0x5521D27: gdk_threads_dispatch (gdk.c:788)
==18357== by 0x5F62A02: g_timeout_dispatch (gmain.c:4413)
==18357== by 0x5F61EA5: g_main_context_dispatch (gmain.c:3054)
==18357== by 0x5F621F7: g_main_context_iterate.isra.22 (gmain.c:3701)
==18357== by 0x5F625F9: g_main_loop_run (gmain.c:3895)
==18357== by 0x4FBE44C: gtk_main (gtkmain.c:1156)
I have fixed this one and sent a merge request upstream, see:
https://code.launchpad.net/~a-j-buxton/lightdm-gtk-greeter/clockleak/+merge/201074
==18357== 8,294,400 bytes in 1 blocks are still reachable in loss
record 6,587 of 6,587
==18357== at 0x4C294A0: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==18357== by 0x57920FC: gdk_pixbuf_new (in
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2800.2)
==18357== by 0xF85B2E5: ??? (in
/usr/lib/x86_64-linux-gnu/librsvg-2.so.2.40.0)
==18357== by 0xF85BF57: rsvg_handle_get_pixbuf_sub (in
/usr/lib/x86_64-linux-gnu/librsvg-2.so.2.40.0)
==18357== by 0xF62FE45: ??? (in
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so)
==18357== by 0x5795FC8: ??? (in
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2800.2)
==18357== by 0x579618B: gdk_pixbuf_new_from_file (in
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2800.2)
==18357== by 0x10FBDD: main (in /usr/sbin/lightdm-gtk-greeter.real)
This is the background pixmap. 1920*1080*4 = 8,294,400. This is
intentionally "leaked".
On 9 January 2014 17:37, Zlatko Calusic <zcalusic@bitsync.net> wrote:
> On 09.01.2014 07:46, Yves-Alexis Perez wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> On Thu, Jan 09, 2014 at 06:23:46AM +0000, Alistair Buxton wrote:
>>>
>>> Hi,
>>>
>>> Please install debug symbols for glib and gdk and then rerun valgrind
>>> with:
>>> --leak-check=full --show-leak-kinds=all
>>
>>
>> In order to do that on Debian, you'll need libglib2.0-0-dbg and
>> libgtk-3-0-dbg.
>>
>
> Packages with symbols installed, new valgrind log attached. Still default
> config, run greeter for about 7-8 hours.
>
> Regards,
> --
> Zlatko
--
Alistair Buxton
a.j.buxton@gmail.com
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Thu, 09 Jan 2014 19:03:09 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Thu, 09 Jan 2014 19:03:10 GMT) (full text, mbox, link).
Message #80 received at 734526@bugs.debian.org (full text, mbox, reply):
On 09.01.2014 19:52, Alistair Buxton wrote:
> Thanks.
>
> ==18357== 4,419,486 bytes in 245,527 blocks are definitely lost in
> loss record 6,586 of 6,587
> ==18357== at 0x4C294A0: malloc (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==18357== by 0x6A7FEF7: __vasprintf_chk (vasprintf_chk.c:80)
> ==18357== by 0x5FA0A4B: g_vasprintf (stdio2.h:210)
> ==18357== by 0x5F7ED5F: g_strdup_vprintf (gstrfuncs.c:517)
> ==18357== by 0x5F7EDFB: g_strdup_printf (gstrfuncs.c:543)
> ==18357== by 0x112186: ??? (in /usr/sbin/lightdm-gtk-greeter.real)
> ==18357== by 0x5521D27: gdk_threads_dispatch (gdk.c:788)
> ==18357== by 0x5F62A02: g_timeout_dispatch (gmain.c:4413)
> ==18357== by 0x5F61EA5: g_main_context_dispatch (gmain.c:3054)
> ==18357== by 0x5F621F7: g_main_context_iterate.isra.22 (gmain.c:3701)
> ==18357== by 0x5F625F9: g_main_loop_run (gmain.c:3895)
> ==18357== by 0x4FBE44C: gtk_main (gtkmain.c:1156)
>
> I have fixed this one and sent a merge request upstream, see:
> https://code.launchpad.net/~a-j-buxton/lightdm-gtk-greeter/clockleak/+merge/201074
>
Thank you Alistair, you're quick! Yves-Alexis, let me know when you have
uploaded version with this fix included, whenever it is (no hurry), so I
can retest and report.
Regards,
--
Zlatko
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 07 May 2014 06:27:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 07 May 2014 06:27:04 GMT) (full text, mbox, link).
Message #85 received at 734526@bugs.debian.org (full text, mbox, reply):
On 09.01.2014 19:58, Zlatko Calusic wrote:
> On 09.01.2014 19:52, Alistair Buxton wrote:
>> Thanks.
>>
>> ==18357== 4,419,486 bytes in 245,527 blocks are definitely lost in
>> loss record 6,586 of 6,587
>> ==18357== at 0x4C294A0: malloc (in
>> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
>> ==18357== by 0x6A7FEF7: __vasprintf_chk (vasprintf_chk.c:80)
>> ==18357== by 0x5FA0A4B: g_vasprintf (stdio2.h:210)
>> ==18357== by 0x5F7ED5F: g_strdup_vprintf (gstrfuncs.c:517)
>> ==18357== by 0x5F7EDFB: g_strdup_printf (gstrfuncs.c:543)
>> ==18357== by 0x112186: ??? (in /usr/sbin/lightdm-gtk-greeter.real)
>> ==18357== by 0x5521D27: gdk_threads_dispatch (gdk.c:788)
>> ==18357== by 0x5F62A02: g_timeout_dispatch (gmain.c:4413)
>> ==18357== by 0x5F61EA5: g_main_context_dispatch (gmain.c:3054)
>> ==18357== by 0x5F621F7: g_main_context_iterate.isra.22 (gmain.c:3701)
>> ==18357== by 0x5F625F9: g_main_loop_run (gmain.c:3895)
>> ==18357== by 0x4FBE44C: gtk_main (gtkmain.c:1156)
>>
>> I have fixed this one and sent a merge request upstream, see:
>> https://code.launchpad.net/~a-j-buxton/lightdm-gtk-greeter/clockleak/+merge/201074
>>
>>
>
> Thank you Alistair, you're quick! Yves-Alexis, let me know when you have
> uploaded version with this fix included, whenever it is (no hurry), so I
> can retest and report.
>
> Regards,
You can close this bug, now. I don't see any memory leaks in the latest
sid versions of lightdm-gtk-greater. Thanks!
--
Zlatko
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 07 May 2014 11:15:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Yves-Alexis Perez <corsac@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 07 May 2014 11:15:04 GMT) (full text, mbox, link).
Message #90 received at 734526@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On mer., 2014-05-07 at 08:19 +0200, Zlatko Calusic wrote:
> You can close this bug, now. I don't see any memory leaks in the latest
> sid versions of lightdm-gtk-greater. Thanks!
Any idea when it stopped? :)
--
Yves-Alexis
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#734526; Package lightdm-gtk-greeter.
(Wed, 07 May 2014 11:54:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Wed, 07 May 2014 11:54:04 GMT) (full text, mbox, link).
Message #95 received at 734526@bugs.debian.org (full text, mbox, reply):
On 07.05.2014 13:11, Yves-Alexis Perez wrote:
> On mer., 2014-05-07 at 08:19 +0200, Zlatko Calusic wrote:
>> You can close this bug, now. I don't see any memory leaks in the latest
>> sid versions of lightdm-gtk-greater. Thanks!
>
> Any idea when it stopped? :)
>
Not really.
--
Zlatko
Reply sent
to Yves-Alexis Perez <corsac@debian.org>:
You have taken responsibility.
(Wed, 07 May 2014 12:21:10 GMT) (full text, mbox, link).
Notification sent
to Zlatko Calusic <zcalusic@bitsync.net>:
Bug acknowledged by developer.
(Wed, 07 May 2014 12:21:10 GMT) (full text, mbox, link).
Message #100 received at 734526-done@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Version: 1.8.2-1
On mer., 2014-05-07 at 13:50 +0200, Zlatko Calusic wrote:
> On 07.05.2014 13:11, Yves-Alexis Perez wrote:
> > On mer., 2014-05-07 at 08:19 +0200, Zlatko Calusic wrote:
> >> You can close this bug, now. I don't see any memory leaks in the latest
> >> sid versions of lightdm-gtk-greater. Thanks!
> >
> > Any idea when it stopped? :)
> >
>
> Not really.
>
Looking at https://launchpad.net/lightdm-gtk-greeter/+milestone/1.8.2 I
guess it's 1.8.2 :)
Regards,
--
Yves-Alexis
[signature.asc (application/pgp-signature, inline)]
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Thu, 05 Jun 2014 07:29:17 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Tue Jul 23 18:15:48 2024;
Machine Name:
bembo
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.