[geos-devel] Memory Management Fixes

[Martin Davis]

There are two memory management issues that I'm aware of:

1. changing PrecisionModel to be a value type, so that deleting Geometries doesn't leak memory
2. ensure that all memory allocated during Geometry methods is freed correctly, including during  exception propagation

1. is pretty easy, and in fact I think Yury mentioned today that he had already implemented this fix.  Yury can confirm this, and if he does RR should test that the fix works

2 is much more work, and is slated to be started once the basic port of the code has been completed (which sounds like it should be done in a week or two).

Yury, I assume that the basic deletion of Geometrys is working (e.g. freeing the pointlists and envelopes) ?

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: Paul Ramsey [mailto:pramsey at refractions.net]
> Sent: Friday, May 30, 2003 4:12 PM
> To: geos-devel at geos.refractions.net
> Subject: [geos-devel] Memory Management Fixes
> 
> 
> What's the ETA on getting the memory management fixed so we 
> can safely 
> delete geometries? Until we get that we cannot cut a beat release of 
> GEOS for use with the PostGIS 0.8 beta.
> Thanks,
> Paul
> 
> 
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel
>