On Tue, 10 Feb 2009, Dirk-Lüder Kreie wrote:
So this did not surface earlier because of frequent updates to the
client, which are less often now. As a workaround one could implement an
automatic restart (and perhaps update of externals) every couple of days.
Better find the unfreed memory instead of working around.
I agree, but seeing that I currently not have time I suggested a
workaround. Other suspects for leaking memory: ImageMagic, LibGD, and
perhapy orp (unlikely).
If we hide the issue, nobody will fix it. I'm against that workaround.
Each one may do that in private installations.
I will try to do a bit debugging for that next wekks, as I anyway need to
learn how to debug memory usage of Perl :-)
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
_______________________________________________
Tilesathome mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/tilesathome
