[Mapserver-dev] Speaking of memory leaks ...

[Sean Gillies]

Steve,

Use "leaks".  I've found Drawin-PPC's memory management to be a bit
more forgiving, so I'm not sure what you'll find.  I haven't gotten
around to fully checking the unit tests on OS X.

Sean

On Sep 30, 2004, at 3:24 PM, Steve Lime wrote:

> Thanks for all the hard work. Any clues as to the location of those
> leaks? I suspect they should both be easy to fix, but I don't have
> valgrind on my Mac...
>
> Steve
>
>>>> Sean Gillies <sgillies at frii.com> 9/27/2004 3:11:09 PM >>>
> As some of you know, I've been out here on the bleeding edge of
> long-running mapserver processes for a while ... and although I'm
> not going to use fastcgi I am grateful for the company. :)
>
> I'm running the Python mapscript unit tests under valgrind.  There
> are pervasive leaks with msSHPOpen() and msAddLabel().  Other than
> this, I'm not finding leaks in the core of mapserver.  I've cleaned
> up every mapscript leak that I've found in the CVS HEAD (4.3).
> Am not doing any tests with rasters or OGR.  Just shapefiles and
> inline
> feature layers.
>
> Sean
>
> --
> Sean Gillies
> sgillies at frii dot com
> http://users.frii.com/sgillies
>
> _______________________________________________
> Mapserver-dev mailing list
> Mapserver-dev at lists.gis.umn.edu
> http://lists.gis.umn.edu/mailman/listinfo/mapserver-dev
>