Another memleak in glib bindings

John (J5) Palmieri johnp at
Fri Mar 17 08:16:58 PST 2006

Unfortunately if you have a pointer in there you are still going to
leak.  Only boxed, string and object types would be guaranteed to be
freed correctly.  Is there any way an untyped pointer could become part
of the array?  Perhaps we should assert on pointers?

On Fri, 2006-03-17 at 11:45 +0100, Jakub Stachowski wrote:
> Hello,
> Trying to send (or receive) array of complex types leads to quite big memory 
> leak. In this case array is represented as GPtrArray and its contents are 
> never freed after use. My application that sends/receives structs a lot grows 
> ~70MB overnight :-(
> Bugzilla entry is
> with proposed patch (by Rob Taylor, I only added finishing touches) :
> _______________________________________________
> dbus mailing list
> dbus at

More information about the dbus mailing list