https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5858
--- Comment #3 from Justin Mason <[EMAIL PROTECTED]> 2008-03-20 10:33:52 PST --- hi -- I think you've run into a problem with perl itself; as far as I know, whether or not the perl interpreter returns freed memory to the OS, is up to the malloc() library in use. In my experience on Linux, it never returns this memory (or at least never returns in a way visible to "ps" or "top"). We get around this in spamd (and our mass-check script) by using child processes to do the check() operations, which exit after scanning several hundred messages. this way the "spare" memory usage is cleaned up when each child exits. There's a possibility btw that the "spare" memory usage is more or less harmless -- in that it is unused by the process after it is freed by perl, and therefore paged out once there's any swap pressure. but it's certainly not good to have. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
