Bug#734526: [Pkg-xfce-devel] Bug#734526: Bug#734526: Bug#734526: lightdm-gtk-greeter: leaking memory
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
Bug#734526: [Pkg-xfce-devel] Bug#734526: Bug#734526: Bug#734526: lightdm-gtk-greeter: leaking memory
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 zcalu...@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 +, 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.bux...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734526: [Pkg-xfce-devel] Bug#734526: Bug#734526: Bug#734526: lightdm-gtk-greeter: leaking memory
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734526: [Pkg-xfce-devel] Bug#734526: Bug#734526: Bug#734526: lightdm-gtk-greeter: leaking memory
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, Jan 09, 2014 at 06:23:46AM +, 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- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
