On Mon, Mar 08, 2004 at 12:11:39PM -0500, Theo Van Dinter wrote: > On Mon, Mar 08, 2004 at 10:48:50AM -0600, Michael Parker wrote: > > Deep recursion on subroutine > > "Mail::SpamAssassin::Message::Node::content_summary" at > > /home/parker/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Message/Node.pm > > line 423. > > Out of memory! > > Hrm. The only rule which uses that is the MPART_ALT_DIFF code. I guess > it depends what is meant by "deep recursion" -- ie: how many times > it that? ;) >
Not totally sure, but I just did it again, and the load average got up around 13 and mass-check had sucked up 775megs of RAM. > > some ideas. Also, given that I know the msgid of the last message > > written to the logs, how do I find which message would be next up for > > processing? > > Heh. It's unfortunately not that easy. You'd need the list of messages, > which doesn't get output in any useful way... You can edit the code in > ArchiveIterator to not unlink the temp file. Then that would tell you > the messages in order. I ended up hacking up wanted to print out the message id right after the message was parsed. So now I've got the message that is causing the problem. I attached the message to Bug 3144. Michael
