[geos-devel] PostGIS Leak

[Yury A. Bychkov]

Strangely enough your example runs fine on my system and I get no segfault while
printing the point.

Yury

P.S. Sorry for the delay, but Monday is my "busy" day


----- Original Message ----- 
From: "strk" <strk at keybit.net>
To: "GEOS Development List" <geos-devel at geos.refractions.net>
Cc: <me at yury.ca>
Sent: Monday, October 20, 2003 11:56 PM
Subject: Re: [geos-devel] PostGIS Leak


> Can you try reproducing the bug I reported about WKTPrinting a point
> geometry ? I can't understant if that is a problem with my environment.
>
> --strk;
>
> me wrote:
> > I wonder if that leak could also be caused by the caching problem (from
> > libstdc++ smart memory management). Unfortunately (as all of you probably
know
> > by now), my leak detector doesn't detect that. Can anyone with valgrind
check if
> > that is the case?
> >
> > Yury
> > ----- Original Message ----- 
> > From: "strk" <strk at keybit.net>
> > To: "GEOS Development List" <geos-devel at geos.refractions.net>
> > Sent: Monday, October 20, 2003 10:47 AM
> > Subject: Re: [geos-devel] PostGIS Leak
> >
> >
> > > pramsey wrote:
> > > > About the PostGIS/GEOS leak I reported, I do not know if I quantified it
> > > > in my email. Even though I was only running isvalid() with a limit of
> > > > 100, I was adding over 1Mb of size to the postgres backend with each
> > > > invocation. So, not a memory leak so much as a memory deluge. Could we
> > > > have a bad PostGIS/GEOS interface now, after some of the GEOS changes?
> > > > Paul
> > >
> > > Yes. May be. I'll check tomorrow (tuesday).
> > >
> > >
> > > --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