Как понимать и фиксить вот такой выхлоп Valgrind?
==28104== 36,480 (15,360 direct, 21,120 indirect) bytes in 60 blocks are definitely lost in loss record 25,222 of 25,306
==28104== at 0x4C2C080: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==28104== by 0x782C6F1: g_malloc0 (in /usr/lib/libglib-2.0.so.0.4400.0)
==28104== by 0x78155A7: g_hash_table_resize (in /usr/lib/libglib-2.0.so.0.4400.0)
==28104== by 0x7815C8E: g_hash_table_insert_node (in /usr/lib/libglib-2.0.so.0.4400.0)
==28104== by 0x7815DC5: g_hash_table_insert_internal (in /usr/lib/libglib-2.0.so.0.4400.0)
==28104== by 0x7B0AC7F: dbus_menu_property_store_new (dbusmenu.vala:81)
==28104== by 0x7B0B109: dbus_menu_item_construct (dbusmenu.vala:139)
==28104== by 0x7B0CDF0: dbus_menu_client_parse_layout (dbusmenu.vala:349)
==28104== by 0x7B0CD63: dbus_menu_client_parse_layout (dbusmenu.vala:313)
==28104== by 0x7B0D520: dbus_menu_client_layout_update_co (dbusmenu.vala:293)
==28104== by 0x7B0DA90: dbus_menu_client_construct (dbusmenu.vala:243)
==28104== by 0x7B11632: dbus_menu_gtk_client_construct (dbusmenu.vala:1036)
==28104== by 0x16F03E02: status_notifier_item_setup_inner_menu (snitem.vala:233)
==28104== by 0x16F03E02: status_notifier_item_init_proxy_co (snitem.vala:115)
==28104== by 0x4EA95C6: g_simple_async_result_complete (in /usr/lib/libgio-2.0.so.0.4400.0)
==28104== by 0x4EA9628: complete_in_idle_cb (in /usr/lib/libgio-2.0.so.0.4400.0)
==28104== by 0x7826C0C: g_main_context_dispatch (in /usr/lib/libglib-2.0.so.0.4400.0)
==28104== by 0x7826FA7: g_main_context_iterate.isra.29 (in /usr/lib/libglib-2.0.so.0.4400.0)
==28104== by 0x782704B: g_main_context_iteration (in /usr/lib/libglib-2.0.so.0.4400.0)
==28104== by 0x4EDC99B: g_application_run (in /usr/lib/libgio-2.0.so.0.4400.0)
==28104== by 0x407365: vala_panel_main (application.vala:38)
==28104== by 0x80597FF: (below main) (in /usr/lib/libc-2.21.so)
==28104==