Memory leak in dbus server connections
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
repowerd |
Fix Committed
|
Medium
|
Alexandros Frantzis |
Bug Description
For example:
valgrind --show-
==18796== 187 (40 direct, 147 indirect) bytes in 1 blocks are definitely lost in loss record 943 of 992
==18796== at 0x4C2EB45: calloc (vg_replace_
==18796== by 0x54709E0: g_malloc0 (in /lib/x86_
==18796== by 0x4F070CF: ??? (in /usr/lib/
==18796== by 0x546E7F2: ??? (in /lib/x86_
==18796== by 0x546F8DA: g_markup_
==18796== by 0x4F07E56: g_dbus_
==18796== by 0x5E1BA9: repowerd:
==18796== by 0x5E2838: std::_Function_
==18796== by 0x4D3FCD: std::function<void ()>::operator()() const (functional:2127)
==18796== by 0x5E9214: (anonymous namespace)
==18796== by 0x546B229: g_main_
==18796== by 0x546B5DF: ??? (in /lib/x86_
This is caused by an upstream gdbus issue tracked here: https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 780924