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
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
