https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6745
Mark Martinec <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #9 from Mark Martinec <[email protected]> 2012-03-27 23:23:44 UTC --- What is common between both submitted logs is that the error occurs in a *parent* spamd process immediately after a child process termination which terminated due to SIGINT: spamd: handled cleanup of child pid [39936] due to SIGCHLD: interrupted, signal 2 The log message is produced by a sub child_handler, which is a signal handling routine: $SIG{CHLD} = \&child_handler; Perl docs warn against doing complex processing while handling a signal, it is considered good practice to just set a flag in a pre-allocated variable and leave the rest to the main program flow. It does not surprise me that an error like "Out of memory" can occur in such a scenario. What I don't know how to better handle the situation. Perhaps just commenting out the call to info() in child_handler would suffice. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
