Comment 5 for bug 751523

This is the valgrind log of gvfsd from my maverick workstation with the bug in full effect. Leaking 1.5GB took about 30 minutes. Here's the relevant part:

==18126== 1,590,801,664 (1,795,104 direct, 1,589,006,560 indirect) bytes in 9,756 blocks are definitely lost in loss record 480 of 480
==18126== at 0x4C2815C: malloc (vg_replace_malloc.c:236)
==18126== by 0x57B965A: dbus_message_new_empty_header (dbus-message.c:1079)
==18126== by 0x57BD1C7: dbus_message_new_method_return (dbus-message.c:1241)
==18126== by 0x4085E7: dbus_message_function (mount.c:927)
==18126== by 0x57BEE4D: _dbus_object_tree_dispatch_and_unlock (dbus-object-tree.c:858)
==18126== by 0x57B248B: dbus_connection_dispatch (dbus-connection.c:4691)
==18126== by 0x4175E4: message_queue_dispatch (dbus-gmain.c:127)
==18126== by 0x5C41341: g_main_context_dispatch (gmain.c:2149)
==18126== by 0x5C452A7: g_main_context_iterate (gmain.c:2780)
==18126== by 0x5C457B4: g_main_loop_run (gmain.c:2988)
==18126== by 0x409099: main (main.c:128)