The main leak there seems to be: ==12580== 10,059,776 bytes in 9,557 blocks are definitely lost in loss record 1,071 of 1,074 ==12580== at 0x4C2B7B2: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==12580== by 0x541DAF6: g_realloc (gmem.c:224) ==12580== by 0x53ECC67: g_ptr_array_maybe_expand (garray.c:1093) ==12580== by 0x53EDC22: g_ptr_array_add (garray.c:1350) ==12580== by 0x4EC77C7: read_netlink_messages (gnetworkmonitornetlink.c:237) ==12580== by 0x4E9F7F5: socket_source_dispatch (gsocket.c:3168) ==12580== by 0x5417C99: g_main_context_dispatch (gmain.c:2515) ==12580== by 0x541805F: g_main_context_iterate.isra.23 (gmain.c:3123) ==12580== by 0x5418459: g_main_loop_run (gmain.c:3317) ==12580== by 0x402EA8: main (whoopsie.c:934)
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/998521 Title: whoopsie process is leaking memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/998521/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
