Pyzor processes stalling

[Achton N. N. <ac...@ne...>]

I'm using amavisd-new and Spamassassin to invoke Pyzor, but recently the 
Pyzor processes have not been ending properly, thus leaving several 
Pyzor processes behind in the course of a single day, and eventually 
causing the swap disk area in RAM to fill up.

This is an example from my processlist:

isildur:~# ps aux
amavis   16177  0.0  1.4 14716 3636 ?        S    Apr12   0:00 
/usr/bin/python /usr/bin/pyzor check
amavis   16276  0.0  1.4 14716 3636 ?        S    Apr12   0:00 
/usr/bin/python /usr/bin/pyzor check
amavis   16894  0.0  1.4 14716 3636 ?        S    Apr12   0:00 
/usr/bin/python /usr/bin/pyzor check
amavis   17020  0.0  1.4 14736 3656 ?        S    Apr12   0:00 
/usr/bin/python /usr/bin/pyzor check
amavis   17502  0.0  1.4 14716 3636 ?        S    Apr12   0:00 
/usr/bin/python /usr/bin/pyzor check
amavis   17678  0.0 14.9 42176 38364 ?       S    Apr12   0:03 amavisd 
(child)
amavis   17725  0.0  1.4 14716 3636 ?        S    Apr12   0:00 
/usr/bin/python /usr/bin/pyzor check
amavis   18222  0.0 14.8 41956 38244 ?       S    00:20   0:00 amavisd 
(child)
amavis   18410  0.0  1.4 14716 3636 ?        S    00:40   0:00 
/usr/bin/python /usr/bin/pyzor check

Running a manual Pyzor check seems to go fine:

isildur:~# pyzor check < /root/testmail
66.250.40.33:24441      (200, 'OK')     0       0

I'm running Debian Sarge on a 550MHz P3 with 256MB RAM.

What can be the cause of this?

Thanks,
Achton

-- 
http://achton.netherclift.net/