[gtk-list] Re: Memory leaks in glib from GTK+ 1.0.6

[eric dahlman <dahlman cs colostate edu>]

Owen Taylor writes:
 > 
[stuff about memory leaks and Glist snipped]
 > 
 > (Note that there quite a few static structurs in GTK+ that
 >  are allocated once and kept around ever after. Since everything
 >  is freed upon exit anyways, there is little point to 
 >  trying to free() these structures before exiting. This may
 >  make it a little difficult to try and trace memory usage
 >  with dmalloc. Commercial tools basically do GC-style checks
 >  so they can identify blocks that cannot be reached at all)

In my spare time [like there is any :-)] I am trying to write a set of 
bindings for GTK+ for Common Lisp and this type of thing keeps biting 
me.  I may just be spoiled, but the way I am accustomed to working with 
GUIs under Lisp allows me to stop/start/restart the thing over and
over.  However, this causes memory leaks in this case since I
cannot explicitly free this memory and the GC won't reclaim memory
allocated in C.  I am sure that this is not a large amount of space
but it is kind of annoying to know it is there.

-Eric

 > 
 > Regards,
 >                                         Owen
 > 
 > -- 
 > To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
 > 
 >