[geos-devel] Memory leak

[Martin Davis]

Currently the priority is porting JTS 1.3 to the GEOS codebase.  Memory issues will be addressed after that.  A rough estimate of when we'll start that work is mid-June.

Martin Davis, Senior Technical Architect
Vivid Solutions Inc.
Suite #1A-2328 Government Street   Victoria, B.C.   V8T 5G5
Phone: (250) 385 6040    Fax: (250) 385 6046
EMail: mbdavis at vividsolutions.com  Web: www.vividsolutions.com


> -----Original Message-----
> From: Martin Müller [mailto:mmueller at intevation.de]
> Sent: Friday, May 09, 2003 3:08 AM
> To: geos-devel at geos.refractions.net
> Subject: [geos-devel] Memory leak
> 
> 
> Hi there,
> 
> thank you for the good job you have done till now, and keep it on.
> I just want to get some information about the memory leak problems in
> geos. 
> I'm developing an SFSQL compliant database interface for a geodata
> viewer called thuban as diploma thesis. To make it SFSQL 
> compliant I had
> to use the cvs version of postgis with geos. 
> Everything except for the memory leak seems to work fine, but I can't
> test thuban with big maps. If I do a few redraws to fit it to the
> canvas, or to zoom into the map, I have to select all geometries in a
> region by using the intersects() function. That makes the postmaster
> process run out of memory very fast.
> If you are interested in thuban, you can get more information at
> http://thuban.intevation.de The cvs doesn't contain thuban with the
> database interface at the moment, but it will released as a branch in
> some days I think. The branch will be merged later on.
> 
> So, when do you think you will fix the leak in geos?
> 
> Thanx for the help,
> 
> 	Martin Müller
> 
> 
> -- 
> _______________________________
> "Microsoft isn't evil, they just make 
> realy crappy operating systems." 
> 
> Linus Torwalds
>