Daemon using dbus to send messages seems to use lots of memory without release them.

[Simon McVittie]

On 25/12/12 07:21, Croach wrote:
> I have updated the program we tested with Valgrind.
> We use glib-2.28.8, dbus-glib-0.100.

For GLib applications, I strongly recommend using GDBus (part of GIO
since 2.26) instead of dbus-glib and libdbus.

Note that the current stable version of GLib is 2.34.something.

>> I have do porting dbus-1.6.4 to a embedded system

The 1.6.x branch is the current stable branch, but the current release
of dbus on that branch is 1.6.8. Please do not target obsolete versions
of a particular branch unless you have an extremely good reason to do so.

In particular, newer versions of dbus 1.6.x have security-sensitive
changes (which avoid local privilege escalation, potentially to root, if
used in a vulnerable setuid executable).

>> I have put the following sample program to a function and run it for
>> 10000 times with Valgrind.

If you're running any libdbus-using application under valgrind, please
check out dbus master from git and read README.valgrind. That
documentation is new since 1.6, but some of the same advice applies
equally to 1.6; it might be necessary to test against master to get
meaningful results.

Having followed the instructions there, it should be possible to get
meaningful Valgrind results and find out what is leaking.

    S