[geos-devel] Leaks are gone

[strk]

me wrote:
> I've just fixed that Empty Polygon memory leak (new code is in CVS), but since
> my leak finder can't detect still reachable blocks, the caching question still
> stands.

Everything sounds leak-free to me.
I'm pretty sure the caching question is an actual bug of my compiler. 
I'll get a stable version of it and see what happen.

--strk;

> 
> Yury
> 
> ----- Original Message ----- 
> From: "strk" <strk at keybit.net>
> To: <geos-devel at geos.refractions.net>
> Cc: <pramsey at refractions.net>
> Sent: Thursday, October 16, 2003 6:10 AM
> Subject: [geos-devel] Leaks are gone
> 
> 
> > Well, almost ;)
> > There is a 32bytes definitely lost running XMLTester on the
> > test data provided by Yury. Allocated bytes are for an Empty
> > LineString forming an Empty Polygon. Yury, any help on this ?
> > Does XMLTester fail to delete Geometries resulting from EMPTY
> > XML reads ?
> >
> > Then - I get from valgrind notice of 480492 bytes in 23 blocks
> > still reachable. XMLTester is now using Unload::Release(), so
> > we might be facing libstdc++ smart memory caching / bugus
> > released version here. Can anybody else try this version ?
> >
> > --strk;
> >
> >
> > _______________________________________________
> > geos-devel mailing list
> > geos-devel at geos.refractions.net
> > http://geos.refractions.net/mailman/listinfo/geos-devel
> 
> 
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel