dbus-glib memory leak or ...? without GMainLoop?
thockin at hockin.org
Sat Feb 20 11:10:08 PST 2010
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.
> 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.
> Here's where I depart from the example code: I do not use GMainLoop.
> This is overall not a glib application and dbus is a retrofit feature
> not a fundamental aspect. I just want to send a dbus signal when my
> app takes a particular event.
> Is that the problem? Can I run a dbus-glib app without GMainLoop?
I converted it to use GMainloop and my server still runs away with
memory, but only when a client is actually listening. I am at a
complete loss on this. What is the dbus-daemon sending back to the
server when a client is connected? How can I instrument this?
More information about the dbus