[Tilecache] Tilecache 2.0.1 Segfault

[Christopher Schmidt]

On Wed, Mar 19, 2008 at 12:34:21PM -0500, Steve Lime wrote:
> The backtrace output is below. I don't think it tells me much. It's dying in MapServer but I think it's because
> there simply isn't any more memory to allocate so a small malloc fails (there is no error check) and then the
> fread causes the segfault. The question is why there is no memory. When I run the seeding the python
> process the python process memory usage swells to 1.4Gb. I've tried with and without metatiling, same
> result. There must be a leak someplace. Any idea how to debug?

Yeah, clearly there's a memory leak: I don't hae any idea where it is
though, nor do I have any suggestions on how to debug. Keeping the map
object open might actually help in this case, because if there's a leak
somewhere in the mapObj open (something not gtting freed), it would be
less prominent if we weren't constantly recreating the mapObj, yeah? 

Regards,
-- 
Christopher Schmidt
MetaCarta