Another memleak in glib bindings

Robert McQueen robert.mcqueen at
Fri Mar 17 08:44:24 PST 2006

You already can't get dbus-binding-tool create you bindings which use a
parameterised type for something which has no free method, it has an
assert for this. In general, a pointer types doesn't have a free method
unless they're boxed, in which case it's fine, but you'll never arrive
into this situation otherwise.


John (J5) Palmieri wrote:
> 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