Just got a much more interesting valgrind run. Juicy excerpt: ==9366== 147,560 bytes in 1,190 blocks are still reachable in loss record 187 of 188 ==9366== at 0x402B965: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==9366== by 0x408E730: dbus_malloc0 (dbus-memory.c:572) ==9366== by 0x407983B: dbus_message_new_empty_header (dbus-message.c:1153) ==9366== by 0x4079D0F: dbus_message_new_method_return (dbus-message.c:1319) ==9366== by 0x80835F5: control_emit_event_reply (com.ubuntu.Upstart.c:2098) ==9366== by 0x806BC6C: event_finished (event.c:501) ==9366== by 0x806B26F: event_poll (event.c:259) ==9366== by 0x4044B63: nih_main_loop (main.c:609) ==9366== by 0x804D507: main (main.c:688) ==9366== ==9366== 228,394,752 bytes in 2,386 blocks are still reachable in loss record 188 of 188 ==9366== at 0x402BB88: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==9366== by 0x408E778: dbus_realloc (dbus-memory.c:678) ==9366== by 0x408F08C: reallocate_for_length (dbus-string.c:349) ==9366== by 0x408F12B: set_length (dbus-string.c:390) ==9366== by 0x408F1A9: open_gap (dbus-string.c:411) ==9366== by 0x408FA67: copy (dbus-string.c:1198) ==9366== by 0x408FCCE: _dbus_string_copy_len (dbus-string.c:1368) ==9366== by 0x408DCF8: marshal_len_followed_by_bytes (dbus-marshal-basic.c:726) ==9366== by 0x408DD95: marshal_string (dbus-marshal-basic.c:758) ==9366== by 0x408DF60: _dbus_marshal_write_basic (dbus-marshal-basic.c:840) ==9366== by 0x4075CD7: _dbus_type_writer_write_basic_no_typecode (dbus-marshal-recursive.c:1601) ==9366== by 0x40768BB: _dbus_type_writer_write_basic (dbus-marshal-recursive.c:2323) ==9366== ==9366== LEAK SUMMARY: ==9366== definitely lost: 28 bytes in 1 blocks ==9366== indirectly lost: 24 bytes in 1 blocks ==9366== possibly lost: 12,907 bytes in 290 blocks ==9366== still reachable: 228,607,834 bytes in 3,732 blocks ==9366== suppressed: 0 bytes in 0 blocks
** Attachment added: "vg.log" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3877842/+files/vg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
