dbus-glib memory leak or ...? without GMainLoop?

[Colin Walters]

On Sat, Feb 20, 2010 at 7:10 PM, Tim Hockin <thockin at hockin.org> wrote:
> On Fri, Feb 19, 2010 at 4:22 PM, Tim Hockin <thockin at hockin.org> wrote:
>> I've built a trivial dbus server and client.  To test I am just
>> sending a signal in a loop. I'm seeing a memory runaway on the server
>> app.  The interesting thing I see is that it is ONLY when a client is
>> connected that memory runs away.  After a few minutes of continuous
>> sending it is over 1GB of RSS.

By "dbus server" do you mean service on the system/session bus?  Or do you mean
a custom DBusServer instance?  Or do you mean a direct dbus-protocol connection
between two processes?

>> This leads me to believe that there is some sort of response data that
>> libdbus is receiving on my behalf that I am not catching.

I think it's a lot more likely you're not freeing something in one of
the implementation
methods of the service.  Have you tried valgrind?