Re: memory leak with gtk+-2.8.20-r1

["Peter \"Firefly\" Lund" <firefly diku dk>]

On Sun, 6 Aug 2006, Iago Rubio wrote:

> The 'possibly lost' bites means - AFAIK - that exists pointers to the
> interior of the analyzed block that may have pointed to the start of the
> block and have been moved, among other possible causes, such as debug
> padding - where a pointer to an object is returned as the start +
> padding of the memory block as with pymalloc and python debug builds.

GTK+/Gnome doesn't release everything on exit normally -- and that's a 
feature!

Why waste time on piecemeal clean up of things the operating system is 
going to clean up anyway much faster?  You even risk slow paging in from 
swap in order to do that useless clean up!  (I think that used to be a 
real performance bug with Netscape/Mozilla.)

There is an environment variable that can be set to a specific value to 
tell the libraries to clean up their stuff anyway so the leaks in an 
application can stand out.

Can't remember what the variable is called or what value to set it to.

-Peter