Comment 7 for bug 930291

The biggest one is still the same

==7902== 9,926,465 (737,712 direct, 9,188,753 indirect) bytes in 10,246 blocks are definitely lost in loss record 1,562 of 1,562
==7902== at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7902== by 0x5A6ABC8: g_malloc (gmem.c:159)
==7902== by 0x5A7D892: g_slice_alloc (gslice.c:1003)
==7902== by 0x5A7DDD5: g_slice_alloc0 (gslice.c:1029)
==7902== by 0x57FE839: g_type_create_instance (gtype.c:1872)
==7902== by 0x57E2FB8: g_object_constructor (gobject.c:1849)
==7902== by 0x57E4B21: g_object_newv (gobject.c:1632)
==7902== by 0x57E510B: g_object_new (gobject.c:1542)
==7902== by 0x553E8A8: g_dbus_message_new_from_blob (gdbusmessage.c:1685)
==7902== by 0x55497BD: _g_dbus_worker_do_read_cb (gdbusprivate.c:752)
==7902== by 0x54E594C: g_simple_async_result_complete (gsimpleasyncresult.c:744)
==7902== by 0x54E5A7B: complete_in_idle_cb (gsimpleasyncresult.c:756)
==7902== by 0x5A64DD9: g_main_context_dispatch (gmain.c:2510)
==7902== by 0x5A6519F: g_main_context_iterate.isra.23 (gmain.c:3118)
==7902== by 0x5A65599: g_main_loop_run (gmain.c:3312)
==7902== by 0x5547445: gdbus_shared_thread_func (gdbusprivate.c:276)
==7902== by 0x5A867D4: g_thread_proxy (gthread.c:801)
==7902== by 0x5D18E99: start_thread (pthread_create.c:308)
==7902== by 0x601E74C: clone (clone.S:112)