On Tue, 16 Feb 2010, Dietmar Rieder wrote: > >> Regardless, if switching to libumem solves problems, there is surely a >> bug somewhere. Libumem supports some built in debugging features >> which might help to discover the location of the problem. > > ...I suspected that, but unfortunately I do not have the skills nor > resources for debugging this problem, but hopefully there is someone out > there who does... Consult 'man umem_debug'. This documents a UMEM_DEBUG environment variable and some other features which can be used to enable debugging and reporting of issues. It seems that UMEM_DEBUG=default is useful. With this enabled, the software may run a bit slower, but it should report any issues. Allocated data is non-zero so if the software somehow depended on this, then the problem should soon become evident. A portable version of libumem is available from "https://labs.omniti.com/trac/portableumem". Bob -- Bob Friesenhahn bfriesen@..., http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Message
Re: [milter-greylist] memory consumption
2010-02-16 by Bob Friesenhahn
Attachments
- No local attachments were found for this message.